linux-kernel - Re: [PATCH 2/2] MAINTAINERS: Add myself as co-maintainer to fpga mgr framework.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 22 Nov 2016 08:48:57 +0100
From:   Michal Simek <michal.simek@...inx.com>
To:     atull <atull@...nsource.altera.com>,
        Moritz Fischer <moritz.fischer@...us.com>
CC:     <linux-kernel@...r.kernel.org>, <marex@...x.de>,
        <mbrugger@...e.com>, <jgunthorpe@...idianresearch.com>,
        <mike.looijmans@...ic.nl>, <michal.simek@...inx.com>,
        <linux-arm-kernel@...ts.infradead.org>,
        "Moritz Fischer" <mdf@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        <linux-fpga@...r.kernel.org>
Subject: Re: [PATCH 2/2] MAINTAINERS: Add myself as co-maintainer to fpga mgr
 framework.

On 22.11.2016 03:29, atull wrote:
> On Mon, 21 Nov 2016, Moritz Fischer wrote:
> 
>> Add myself as co-maintainer to fpga mgr framework.
>>
>> Signed-off-by: Moritz Fischer <mdf@...nel.org>
>> Cc: Alan Tull <atull@...nsource.altera.com>
>> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>> Cc: linux-kernel@...r.kernel.org
>> Cc: linux-fpga@...r.kernel.org
>> ---
>> Hi all,
>>
>> Lately we've fallen behind a bit on reviewing patches lately.
> 
> Hi Moritz,
> 
> drivers/fpga has been in the upstream kernel a year now.  Most of that
> time, traffic has been very slow.  Recently we had more traffic while
> I was travelling and moving to a new office, both cases leaving me
> with bad network connectivity.  Things will probably return to normal.
> I appreciate your passion and all your effort reviewing stuff.  I
> don't see a need for two maintainers at this point.

TBH. I think it is not a bad option. I do normally have backup person
for all repos I do maintain. It doesn't mean that second maintainer does
something but it has all accesses to repos you maintain.
It means if something really happens to you (hopefully not) than this
person can continue in this work without any delay which is not a bad
thing.
It is really just about talking to each other what that second person
will do - probably just review patches as is done now. You can also
learn from each other.
I would like to be involved more in this but unfortunately I don't have
enough time to do it properly.

Regarding maintaining this repo. It is just standard process. Apply
sensible things, well described and test it. And then send pull request
to Greg based on signed tags and you are done.
Greg should told you what should be the base which you should use for
pull request. Someone is taking patches based on rc1 tag, someone is
rebasing it on the final tag.

Acked-by: Michal Simek <michal.simek@...inx.com>

Thanks,
Michal