Skip to contentSkip to conversation

MAINTAINERS: add Amir as xfs maintainer for 5.10.y

PATCH In review Amir Goldstein 2 participants 4 messages Jun 30, 2022 Stable branch

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 MAINTAINERS: add Amir as xfs maintainer for 5.10.y

This is an attempt to direct the bots and human that are testing LTS 5.10.y towards the maintainer of xfs in the 5.10.y tree.

This is not an upstream MAINTAINERS entry and 5.15.y and 5.4.y will have their own LTS xfs maintainer entries.

Update Darrick's email address from upstream and add Amir as xfs maintaier for the 5.10.y tree.

---

Greg,

We decided to try and fork MAINTAINERS.

I don't know if this was attempted before and I don't know if you think that is a good idea, but the rationale is that at least some of the scripts that report bugs on LTS, will be running get_maintainer.pl on the LTS branch they are testing.

The scripts that run get_maintainer.pl on master can be tought to do the right thing for LTS reporting.
This seems easier and more practical then teaching the scripts to parse LTS specific entries in upstream MAINTAINERS.

You have another patch like that coming fro Leah for 5.15.y.

Thanks,
Amir.

 MAINTAINERS | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
MAINTAINERS +2 -1
index 7c118b507912..4d10e79030a9 100644
@@ -19246,7 +19246,8 @@ F:	arch/x86/xen/*swiotlb*
 F:	drivers/xen/*swiotlb*
 
 XFS FILESYSTEM
-M:	Darrick J. Wong <[email protected]>
+M:	Amir Goldstein <[email protected]>
+M:	Darrick J. Wong <[email protected]>
 M:	[email protected]
 L:	[email protected]
 S:	Supported
Signature · 1 line
2.25.1
#1 lore raw
Quoted 42 lines · Amir Goldstein

This is an attempt to direct the bots and human that are testing LTS 5.10.y towards the maintainer of xfs in the 5.10.y tree.

This is not an upstream MAINTAINERS entry and 5.15.y and 5.4.y will have their own LTS xfs maintainer entries.

Update Darrick's email address from upstream and add Amir as xfs maintaier for the 5.10.y tree.

---

Greg,

We decided to try and fork MAINTAINERS.

I don't know if this was attempted before and I don't know if you think that is a good idea, but the rationale is that at least some of the scripts that report bugs on LTS, will be running get_maintainer.pl on the LTS branch they are testing.

The scripts that run get_maintainer.pl on master can be tought to do the right thing for LTS reporting.
This seems easier and more practical then teaching the scripts to parse LTS specific entries in upstream MAINTAINERS.

You have another patch like that coming fro Leah for 5.15.y.

Thanks,
Amir.

 MAINTAINERS | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
MAINTAINERS +0 -0
index 7c118b507912..4d10e79030a9 100644

MAINTAINERS F: arch/x86/xen/*swiotlb* · line 19253

Quoted 9 lines
MAINTAINERS +2 -1
@@ -19246,7 +19246,8 @@ F:	arch/x86/xen/*swiotlb*
 F:	drivers/xen/*swiotlb*
 
 XFS FILESYSTEM
-M:	Darrick J. Wong <[email protected]>
+M:	Amir Goldstein <[email protected]>
+M:	Darrick J. Wong <[email protected]>
 M:	[email protected]
 L:	[email protected]
 S:	Supported

I'll apply this, but really, no one will ever notice it.

All new patches, and work, goes on on Linus's tree and you have to submit matches for it to be considered for older stable kernels as you know. So there's not much for old MAINTAINERS entries here.

But hey, I could be wrong let's try it and see what happens :)

thanks,

greg k-h

#2 lore raw
Quoted 56 lines · Greg Kroah-Hartman
Quoted 42 lines · Amir Goldstein

This is an attempt to direct the bots and human that are testing LTS 5.10.y towards the maintainer of xfs in the 5.10.y tree.

This is not an upstream MAINTAINERS entry and 5.15.y and 5.4.y will have their own LTS xfs maintainer entries.

Update Darrick's email address from upstream and add Amir as xfs maintaier for the 5.10.y tree.

---

Greg,

We decided to try and fork MAINTAINERS.

I don't know if this was attempted before and I don't know if you think that is a good idea, but the rationale is that at least some of the scripts that report bugs on LTS, will be running get_maintainer.pl on the LTS branch they are testing.

The scripts that run get_maintainer.pl on master can be tought to do the right thing for LTS reporting.
This seems easier and more practical then teaching the scripts to parse LTS specific entries in upstream MAINTAINERS.

You have another patch like that coming fro Leah for 5.15.y.

Thanks,
Amir.

 MAINTAINERS | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
MAINTAINERS +0 -0
index 7c118b507912..4d10e79030a9 100644

MAINTAINERS F: arch/x86/xen/*swiotlb* · line 19253

Quoted 9 lines
MAINTAINERS +2 -1
@@ -19246,7 +19246,8 @@ F:    arch/x86/xen/*swiotlb*
 F:   drivers/xen/*swiotlb*
 
 XFS FILESYSTEM
-M:   Darrick J. Wong <[email protected]>
+M:   Amir Goldstein <[email protected]>
+M:   Darrick J. Wong <[email protected]>
 M:   [email protected]
 L:   [email protected]
 S:   Supported

I'll apply this, but really, no one will ever notice it.

Quoted 5 lines

All new patches, and work, goes on on Linus's tree and you have to submit matches for it to be considered for older stable kernels as you know. So there's not much for old MAINTAINERS entries here.

But hey, I could be wrong let's try it and see what happens :)

Just to be clear, this meant not for CCing stable xfs maintainers on fix patches that developers send upstream.

This is only so bots running on LTS and distro kernels find xfs bugs are advised to CC the xfs stable maintainers.

Thanks,
Amir.

P.S. You have an xfs backport series for both 5.10 and 5.15 in your inbox...

#3 lore raw
Quoted 62 lines · Amir Goldstein
Quoted 60 lines · Greg Kroah-Hartman
Quoted 42 lines · Amir Goldstein

This is an attempt to direct the bots and human that are testing LTS 5.10.y towards the maintainer of xfs in the 5.10.y tree.

This is not an upstream MAINTAINERS entry and 5.15.y and 5.4.y will have their own LTS xfs maintainer entries.

Update Darrick's email address from upstream and add Amir as xfs maintaier for the 5.10.y tree.

---

Greg,

We decided to try and fork MAINTAINERS.

I don't know if this was attempted before and I don't know if you think that is a good idea, but the rationale is that at least some of the scripts that report bugs on LTS, will be running get_maintainer.pl on the LTS branch they are testing.

The scripts that run get_maintainer.pl on master can be tought to do the right thing for LTS reporting.
This seems easier and more practical then teaching the scripts to parse LTS specific entries in upstream MAINTAINERS.

You have another patch like that coming fro Leah for 5.15.y.

Thanks,
Amir.

 MAINTAINERS | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
MAINTAINERS +0 -0
index 7c118b507912..4d10e79030a9 100644

MAINTAINERS F: arch/x86/xen/*swiotlb* · line 19253

Quoted 9 lines
MAINTAINERS +2 -1
@@ -19246,7 +19246,8 @@ F:    arch/x86/xen/*swiotlb*
 F:   drivers/xen/*swiotlb*
 
 XFS FILESYSTEM
-M:   Darrick J. Wong <[email protected]>
+M:   Amir Goldstein <[email protected]>
+M:   Darrick J. Wong <[email protected]>
 M:   [email protected]
 L:   [email protected]
 S:   Supported

I'll apply this, but really, no one will ever notice it.

All new patches, and work, goes on on Linus's tree and you have to submit matches for it to be considered for older stable kernels as you know. So there's not much for old MAINTAINERS entries here.

Quoted 7 lines
Quoted 1 line

But hey, I could be wrong let's try it and see what happens :)

Just to be clear, this meant not for CCing stable xfs maintainers on fix patches that developers send upstream.

This is only so bots running on LTS and distro kernels find xfs bugs are advised to CC the xfs stable maintainers.

Let's see if they even look at that file.

Quoted 2 lines

P.S. You have an xfs backport series for both 5.10 and 5.15 in your inbox...

I have lots of stable patches to catch up on, you are in good company:

	$ mdfrm -c ~/mail/stable/
	186 messages in /home/gregkh/mail/stable/

I'll try to get through them later today

greg k-h