public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Rob Herring <rob.herring@calxeda.com>
Subject: Re: [PATCH] MAINTAINERS: Update Grant's email address and maintainership
Date: Thu, 18 Apr 2013 12:04:39 +0100	[thread overview]
Message-ID: <20130418110439.GB13687@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20130417172134.dea24373a65d78b53cfd3a54@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 566 bytes --]

On Wed, Apr 17, 2013 at 05:21:34PM +1000, Stephen Rothwell wrote:
> On Wed, 17 Apr 2013 08:16:17 +0100 Grant Likely <grant.likely@secretlab.ca> wrote:
> > On Wed, Apr 17, 2013 at 12:52 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> > > Does this have any implications for linux-next included trees or their
> > > contacts?

> > No. My old email address still works, and I'm not changing my git
> > trees anytime soon.

> OK, thanks.

However could you please change my SPI tree to be:

  git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-04-18 11:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 10:43 [PATCH] MAINTAINERS: Update Grant's email address and maintainership grant.likely
2013-04-16 12:32 ` Linus Walleij
2013-04-16 15:19 ` Joe Perches
2013-04-16 23:52 ` Stephen Rothwell
2013-04-17  7:16   ` Grant Likely
2013-04-17  7:21     ` Stephen Rothwell
2013-04-18 11:04       ` Mark Brown [this message]
2013-04-18 23:18         ` Stephen Rothwell
2013-04-19 10:22           ` Mark Brown
2013-04-26  0:50             ` Stephen Rothwell

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=20130418110439.GB13687@opensource.wolfsonmicro.com \
    --to=broonie@kernel.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=sfr@canb.auug.org.au \
    /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