From: Michal Simek <michal.simek@xilinx.com>
To: atull <atull@opensource.altera.com>,
Moritz Fischer <moritz.fischer@ettus.com>
Cc: <linux-kernel@vger.kernel.org>, <marex@denx.de>,
<mbrugger@suse.com>, <jgunthorpe@obsidianresearch.com>,
<mike.looijmans@topic.nl>, <michal.simek@xilinx.com>,
<linux-arm-kernel@lists.infradead.org>,
"Moritz Fischer" <mdf@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-fpga@vger.kernel.org>
Subject: Re: [PATCH 2/2] MAINTAINERS: Add myself as co-maintainer to fpga mgr framework.
Date: Tue, 22 Nov 2016 08:48:57 +0100 [thread overview]
Message-ID: <47eb36a7-ee48-53bd-fbdc-15225c3147ec@xilinx.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611212021050.3633@atull-VirtualBox2>
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@kernel.org>
>> Cc: Alan Tull <atull@opensource.altera.com>
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Cc: linux-kernel@vger.kernel.org
>> Cc: linux-fpga@vger.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@xilinx.com>
Thanks,
Michal
next prev parent reply other threads:[~2016-11-22 8:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 21:49 [PATCH 1/2] MAINTAINERS: Update fpga-mgr entry with new linux-fpga mailing list Moritz Fischer
2016-11-21 21:49 ` [PATCH 2/2] MAINTAINERS: Add myself as co-maintainer to fpga mgr framework Moritz Fischer
2016-11-21 22:09 ` Marek Vasut
2016-11-22 2:29 ` atull
2016-11-22 7:48 ` Michal Simek [this message]
2016-11-22 8:07 ` Greg Kroah-Hartman
2016-11-22 8:28 ` Michal Simek
2016-11-22 16:35 ` Jason Gunthorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47eb36a7-ee48-53bd-fbdc-15225c3147ec@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=atull@opensource.altera.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=mbrugger@suse.com \
--cc=mdf@kernel.org \
--cc=mike.looijmans@topic.nl \
--cc=moritz.fischer@ettus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®