linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Metcalf <cmetcalf@ezchip.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: change of contact address for the tile tree?
Date: Thu, 13 Nov 2014 23:05:58 +0000	[thread overview]
Message-ID: <F21E5D8A-0990-47F3-A89A-01EBA24208DF@ezchip.com> (raw)
In-Reply-To: <20141114100426.6bfa92f8@canb.auug.org.au>


> On Nov 13, 2014, at 6:04 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Hi Chris,
> 
> I noticed commit c47b15c4928c ("arch/tile: update MAINTAINERS email to
> EZchip") in the tile tree today.  Should I update the contact address I
> have for you?
> 

Yes thanks!

  reply	other threads:[~2014-11-13 23:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 23:04 linux-next: change of contact address for the tile tree? Stephen Rothwell
2014-11-13 23:05 ` Chris Metcalf [this message]
2014-11-13 23:25   ` 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=F21E5D8A-0990-47F3-A89A-01EBA24208DF@ezchip.com \
    --to=cmetcalf@ezchip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).