[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <25d1dac2-4f9f-b5f0-8ce8-b88442deac9d@redhat.com>
Date: Wed, 15 Sep 2021 06:23:16 -0700
From: Tom Rix <trix@...hat.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: mdf@...nel.org, hao.wu@...el.com, linux-kernel@...r.kernel.org,
linux-fpga@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add Tom Rix as fpga maintainer
On 9/14/21 11:58 AM, Greg KH wrote:
> [note, you got the maintainer's email address wrong on your cc: line
> I fixed it up...]
>
> On Tue, Sep 14, 2021 at 11:23:33AM -0700, trix@...hat.com wrote:
>> From: Tom Rix <trix@...hat.com>
>>
>> I am the maintainer of the fpga/ subsystem for both the kernel and
>> userspace for Red Hat. I have been an active reviewer and contributor
>> on for public fpga/ subsystem for the last year. I would like to
>> help out more.
>>
>> Since I am paid to do this work, change the status to Supported.
>>
>> Signed-off-by: Tom Rix <trix@...hat.com>
>> ---
>> MAINTAINERS | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 04fa4edf100b83..0443d7ab826659 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -7353,9 +7353,9 @@ F: include/uapi/linux/fpga-dfl.h
>>
>> FPGA MANAGER FRAMEWORK
>> M: Moritz Fischer <mdf@...nel.org>
>> -R: Tom Rix <trix@...hat.com>
>> +M: Tom Rix <trix@...hat.com>
>> L: linux-fpga@...r.kernel.org
>> -S: Maintained
>> +S: Supported
>> W: http://www.rocketboards.org
>> Q: http://patchwork.kernel.org/project/linux-fpga/list/
>> T: git git://git.kernel.org/pub/scm/linux/kernel/git/mdf/linux-fpga.git
>> --
>> 2.26.3
>>
> Traditionally existing maintainers are the ones that add new
> maintainers, it's not something that you just submit a patch for hoping
> it will be accepted.
>
> What has changed since the last time you asked to do this?
Because public and private requests have gone unanswered for so long, it
is unclear if Moritz is still maintaining the subsystem.
The nearly year old xrt patchset has been pending for 6 weeks with minor
changes to one patch out of 14 needing reviews.
The standard release patchset, which needs an opinion has on an api
change, has been outstanding for 8 weeks.
If maintainership depends on an approving maintainter, what happens when
the approving maintainer has left ?
Tom
>
> thanks,
>
> greg k-h
>
Powered by blists - more mailing lists