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.
Suggested-by: Darrick J. Wong djwong@kernel.org Link: https://lore.kernel.org/linux-xfs/Yrx6%2F0UmYyuBPjEr@magnolia/ Signed-off-by: Amir Goldstein amir73il@gmail.com Reviewed-by: Darrick J. Wong djwong@kernel.org ---
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(-)
diff --git a/MAINTAINERS b/MAINTAINERS index 7c118b507912..4d10e79030a9 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -19246,7 +19246,8 @@ F: arch/x86/xen/*swiotlb* F: drivers/xen/*swiotlb*
XFS FILESYSTEM -M: Darrick J. Wong darrick.wong@oracle.com +M: Amir Goldstein amir73il@gmail.com +M: Darrick J. Wong djwong@kernel.org M: linux-xfs@vger.kernel.org L: linux-xfs@vger.kernel.org S: Supported
On Thu, Jun 30, 2022 at 08:43:21AM +0300, Amir Goldstein wrote:
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.
Suggested-by: Darrick J. Wong djwong@kernel.org Link: https://lore.kernel.org/linux-xfs/Yrx6%2F0UmYyuBPjEr@magnolia/ Signed-off-by: Amir Goldstein amir73il@gmail.com Reviewed-by: Darrick J. Wong djwong@kernel.org
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(-)
diff --git a/MAINTAINERS b/MAINTAINERS index 7c118b507912..4d10e79030a9 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -19246,7 +19246,8 @@ F: arch/x86/xen/*swiotlb* F: drivers/xen/*swiotlb* XFS FILESYSTEM -M: Darrick J. Wong darrick.wong@oracle.com +M: Amir Goldstein amir73il@gmail.com +M: Darrick J. Wong djwong@kernel.org M: linux-xfs@vger.kernel.org L: linux-xfs@vger.kernel.org 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
On Thu, Jun 30, 2022 at 10:27 AM Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Thu, Jun 30, 2022 at 08:43:21AM +0300, Amir Goldstein wrote:
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.
Suggested-by: Darrick J. Wong djwong@kernel.org Link: https://lore.kernel.org/linux-xfs/Yrx6%2F0UmYyuBPjEr@magnolia/ Signed-off-by: Amir Goldstein amir73il@gmail.com Reviewed-by: Darrick J. Wong djwong@kernel.org
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(-)
diff --git a/MAINTAINERS b/MAINTAINERS index 7c118b507912..4d10e79030a9 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -19246,7 +19246,8 @@ F: arch/x86/xen/*swiotlb* F: drivers/xen/*swiotlb*
XFS FILESYSTEM -M: Darrick J. Wong darrick.wong@oracle.com +M: Amir Goldstein amir73il@gmail.com +M: Darrick J. Wong djwong@kernel.org M: linux-xfs@vger.kernel.org L: linux-xfs@vger.kernel.org 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 :)
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...
On Thu, Jun 30, 2022 at 11:28:37AM +0300, Amir Goldstein wrote:
On Thu, Jun 30, 2022 at 10:27 AM Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Thu, Jun 30, 2022 at 08:43:21AM +0300, Amir Goldstein wrote:
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.
Suggested-by: Darrick J. Wong djwong@kernel.org Link: https://lore.kernel.org/linux-xfs/Yrx6%2F0UmYyuBPjEr@magnolia/ Signed-off-by: Amir Goldstein amir73il@gmail.com Reviewed-by: Darrick J. Wong djwong@kernel.org
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(-)
diff --git a/MAINTAINERS b/MAINTAINERS index 7c118b507912..4d10e79030a9 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -19246,7 +19246,8 @@ F: arch/x86/xen/*swiotlb* F: drivers/xen/*swiotlb*
XFS FILESYSTEM -M: Darrick J. Wong darrick.wong@oracle.com +M: Amir Goldstein amir73il@gmail.com +M: Darrick J. Wong djwong@kernel.org M: linux-xfs@vger.kernel.org L: linux-xfs@vger.kernel.org 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 :)
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.
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
linux-stable-mirror@lists.linaro.org