linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Darren Hart <dvhart@infradead.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: the drivers-x86 tree has moved?
Date: Wed, 13 Dec 2017 12:00:39 +1100	[thread overview]
Message-ID: <20171213120039.31eaff80@canb.auug.org.au> (raw)
In-Reply-To: <20171212234330.GK27831@fury>

Hi Darren,

On Tue, 12 Dec 2017 15:43:30 -0800 Darren Hart <dvhart@infradead.org> wrote:
>
> On Wed, Dec 13, 2017 at 08:02:27AM +1100, Stephen Rothwell wrote:
> > 
> > I noticed commit
> > 
> >   960652046899 ("MAINTAINERS: Update tree for platform-drivers-x86")
> > 
> > Should I also change linu-next to use the new tree?  
> 
> The new one is the correct location, but the old one points to it. I don't plan
> to destroy the old link, but updating linux-next to use the new one is a good
> idea.
> 
> So, yes - please do :-)

Done.
-- 
Cheers,
Stephen Rothwell

      reply	other threads:[~2017-12-13  1:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 21:02 linux-next: the drivers-x86 tree has moved? Stephen Rothwell
2017-12-12 23:43 ` Darren Hart
2017-12-13  1:00   ` Stephen Rothwell [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=20171213120039.31eaff80@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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).