linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 14
Date: Mon, 14 May 2018 10:26:07 +0300	[thread overview]
Message-ID: <CAHp75Vfs_Za5d8YLJ5FNJDmytRJE-P+q_Kds9V+ivBGy3v+p8g@mail.gmail.com> (raw)
In-Reply-To: <20180514172042.093bd880@canb.auug.org.au>

On Mon, May 14, 2018 at 10:20 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Changes since 20180511:
>
> New trees: btrfs-fixes
>         vfs-fixes
>         dma-mapping-fixes
>
> The f2fs tree gained a conflict against the vfs-fixes tree.
>
> The bpf-next tree gained a conflict against the bpf tree.
>
> The rcu tree gained a conflict against Linus' tree.
>
> The kselftest tree gained a conflict against the kvm-fixes tree.
>
> Non-merge commits (relative to Linus' tree): 5724
>  5580 files changed, 217262 insertions(+), 101414 deletions(-)
>
> ----------------------------------------------------------------------------
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one.  You should use "git fetch" and checkout or reset to the new
> master.

Hmm... It seems my message was buried in the pile of the thread WRT
fixes branches.

Please, add our PDx86 fixes branch as well:
git://git.infradead.org/linux-platform-drivers-x86.git fixes

-- 
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2018-05-14  7:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14  7:20 Stephen Rothwell
2018-05-14  7:26 ` Andy Shevchenko [this message]
2018-05-14 12:40   ` Stephen Rothwell
2018-05-14 17:14     ` Andy Shevchenko
2018-05-14 21:54       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2021-05-14  5:40 Stephen Rothwell
2020-05-14 11:07 Stephen Rothwell
2019-05-14  4:35 Stephen Rothwell
2015-05-14  8:25 Stephen Rothwell
2014-05-14  8:26 Stephen Rothwell
2013-05-14  4:17 Stephen Rothwell
2012-05-14 10:03 Stephen Rothwell
2010-05-14  6:14 Stephen Rothwell
2009-05-14  6:41 Stephen Rothwell
2009-05-14 13:17 ` Nico -telmich- Schottelius
2008-05-14  7:01 Stephen Rothwell
2008-05-14 20:38 ` Geert Uytterhoeven
2008-05-14 20:50   ` Randy Dunlap
2008-05-14 21:04     ` Tony Breeds
2008-05-15  1:05       ` Tony Breeds
2008-05-15  7:17         ` Geert Uytterhoeven
2008-05-15  7:23           ` Stephen Rothwell
2008-05-16  2:10           ` Tony Breeds
2008-05-16  7:12             ` Geert Uytterhoeven

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=CAHp75Vfs_Za5d8YLJ5FNJDmytRJE-P+q_Kds9V+ivBGy3v+p8g@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --subject='Re: linux-next: Tree for May 14' \
    /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

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).