From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Graf <agraf@suse.de>
Cc: "J. German Rivera" <German.Rivera@freescale.com>,
arnd@arndb.de, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, stuart.yoder@freescale.com,
Kim.Phillips@freescale.com, scottwood@freescale.com,
bhamciu1@freescale.com, R89243@freescale.com,
bhupesh.sharma@freescale.com, nir.erez@freescale.com,
richard.schmitt@freescale.com
Subject: Re: [PATCH] staging: fsl-mc: Corrected email addresses in TODO file
Date: Tue, 17 Mar 2015 08:53:14 +0100 [thread overview]
Message-ID: <20150317075314.GA28026@kroah.com> (raw)
In-Reply-To: <5507D462.4020504@suse.de>
On Tue, Mar 17, 2015 at 08:14:42AM +0100, Alexander Graf wrote:
>
>
> On 12.03.15 04:52, J. German Rivera wrote:
> > Signed-off-by: J. German Rivera <German.Rivera@freescale.com>
>
> Greg, going forward, how would you prefer to get patches for fsl-mc?
> There are a few options that I can see:
>
> 1) individual patches on the ML for review, directly applied by you
> 2) individual patches on the ML for review, regular big patch sets
> from German to you
> 3) individual patches on the ML for review, regular pull requests from
> German to you
>
>
> I would personally prefer either 2 or 3, as that allows German to be the
> gatekeeper and grow responsibility for the upstream tree.
2 is fine, but note that I will pick up "cleanup" patches automatically,
no need for anyone else to be involved, as that's part of being in
staging.
thanks,
greg k-h
prev parent reply other threads:[~2015-03-17 7:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 3:52 [PATCH] staging: fsl-mc: Corrected email addresses in TODO file J. German Rivera
2015-03-17 7:14 ` Alexander Graf
2015-03-17 7:53 ` Greg KH [this message]
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=20150317075314.GA28026@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=German.Rivera@freescale.com \
--cc=Kim.Phillips@freescale.com \
--cc=R89243@freescale.com \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=bhamciu1@freescale.com \
--cc=bhupesh.sharma@freescale.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nir.erez@freescale.com \
--cc=richard.schmitt@freescale.com \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.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