From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 21
Date: Mon, 21 May 2012 08:09:49 -0700 [thread overview]
Message-ID: <4FBA5ABD.2070003@xenotime.net> (raw)
In-Reply-To: <20120521190531.b764b9cd339c883d3434aef8@canb.auug.org.au>
On 05/21/2012 02:05 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 201205018:
> ----------------------------------------------------------------------------
>
> 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/ ).
no linux-next 20120521 patch file :(
--
~Randy
next prev parent reply other threads:[~2012-05-21 15:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 9:05 linux-next: Tree for May 21 Stephen Rothwell
2012-05-21 15:09 ` Randy Dunlap [this message]
2012-05-21 15:41 ` Stephen Rothwell
2012-05-21 15:44 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-05-21 11:20 Stephen Rothwell
2024-05-21 2:54 Stephen Rothwell
2021-05-21 6:44 Stephen Rothwell
2020-05-21 14:12 Stephen Rothwell
2020-05-21 15:09 ` Daniel Thompson
2019-05-21 5:14 Stephen Rothwell
2019-05-21 5:48 ` Masahiro Yamada
2019-05-21 6:18 ` Stephen Rothwell
2015-05-21 8:57 Stephen Rothwell
2014-05-21 7:50 Stephen Rothwell
2014-05-21 7:50 ` Stephen Rothwell
2014-05-22 10:45 ` Michael Kerrisk
2014-05-22 22:06 ` Stephen Rothwell
2014-05-23 4:22 ` Michael Kerrisk (man-pages)
2013-05-21 5:03 Stephen Rothwell
2013-05-21 5:03 ` Stephen Rothwell
2010-05-21 6:51 Stephen Rothwell
2009-05-21 8:14 Stephen Rothwell
2008-05-21 5:59 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=4FBA5ABD.2070003@xenotime.net \
--to=rdunlap@xenotime.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.