From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Xiong Zhou <jencce.kernel@gmail•com>
Cc: Linux-Next <linux-next@vger•kernel.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for May 17
Date: Mon, 23 May 2016 18:37:55 +1000 [thread overview]
Message-ID: <20160523183755.412b335c@canb.auug.org.au> (raw)
In-Reply-To: <CADJHv_tz6NeJtYM4R6R6PQjYm=UL7QM0ErnprzFZORrLY6WDkQ@mail.gmail.com>
Hi Xiong,
On Mon, 23 May 2016 16:13:28 +0800 Xiong Zhou <jencce.kernel@gmail•com> wrote:
>
> hi,
>
> On Tue, May 17, 2016 at 1:04 PM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > 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
>
> Patches after 0516 are not there.
>
> i'm chasing an oom issue between 0516 and 0518 trees while missed
> 0517 tag, so is the patch file the only way to get there trying 0517 tree?
They are there, just the version numbering puts them out of order in the
page listing - they appear before patch-v4.6-rc1-next-20160327.gz
All the (recent) tags are in the git tree as well, of course.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-05-23 8:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 5:04 linux-next: Tree for May 17 Stephen Rothwell
2016-05-23 8:13 ` Xiong Zhou
2016-05-23 8:37 ` Stephen Rothwell [this message]
2016-05-24 4:52 ` Xiong Zhou
-- strict thread matches above, loose matches on Subject: below --
2024-05-17 3:39 Stephen Rothwell
2023-05-17 2:05 Stephen Rothwell
2022-05-17 9:41 Stephen Rothwell
2019-05-17 4:21 Stephen Rothwell
2019-05-17 7:33 ` Anders Roxell
2019-05-17 9:41 ` Kirill Tkhai
2019-05-17 9:43 ` Kirill Tkhai
2019-05-17 9:53 ` Stephen Rothwell
2019-05-17 21:56 ` Palmer Dabbelt
2018-05-17 7:06 Stephen Rothwell
2018-05-17 18:03 ` Naresh Kamboju
2018-05-22 14:18 ` Mark Brown
2018-05-23 23:07 ` Mark Brown
2017-05-17 4:17 Stephen Rothwell
2013-05-17 4:21 Stephen Rothwell
2012-05-17 7:46 Stephen Rothwell
2011-05-17 4:27 Stephen Rothwell
2010-05-17 6:35 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=20160523183755.412b335c@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jencce.kernel@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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