From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Dave Young <hidave.darkstar@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for June 3
Date: Sat, 5 Jun 2010 12:21:37 +0930 [thread overview]
Message-ID: <201006051221.38088.rusty@rustcorp.com.au> (raw)
In-Reply-To: <201006051209.51664.rusty@rustcorp.com.au>
On Sat, 5 Jun 2010 12:09:51 pm Rusty Russell wrote:
> Here's a tree with all current fixes: still no module load?
Erk, terminally broken tree. Will re-xmit once fixed...
Rusty.
next prev parent reply other threads:[~2010-06-05 2:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 3:47 linux-next: Tree for June 3 Stephen Rothwell
2010-06-03 7:39 ` Dave Young
2010-06-03 8:00 ` Dave Young
2010-06-03 8:16 ` Dave Young
2010-06-03 12:52 ` Rusty Russell
2010-06-04 19:46 ` Tony Luck
2010-06-04 20:04 ` Linus Torvalds
2010-06-04 20:46 ` Luck, Tony
2010-06-04 22:05 ` Linus Torvalds
2010-06-04 22:50 ` Luck, Tony
2010-06-04 22:57 ` Linus Torvalds
2010-06-05 2:39 ` Rusty Russell
2010-06-05 2:51 ` Rusty Russell [this message]
2010-06-05 4:01 ` Rusty Russell
2010-06-07 18:16 ` Luck, Tony
2010-06-03 15:46 ` linux-next: Tree for June 3 (qlcnic) Randy Dunlap
2010-06-03 17:31 ` Anirban Chakraborty
2010-06-03 15:55 ` linux-next: Tree for June 3 (iwlwifi) Randy Dunlap
2010-06-03 17:21 ` John W. Linville
2010-06-03 17:42 ` Guy, Wey-Yi
2010-06-03 17:45 ` reinette chatre
2010-06-03 16:39 ` [PATCH -next] classmate-laptop: fix for RFKILL=m, CMPC=y Randy Dunlap
2010-06-09 20:02 ` Thadeu Lima de Souza Cascardo
2010-06-09 20:05 ` Randy Dunlap
2010-06-09 20:11 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2011-06-03 6:38 linux-next: Tree for June 3 Stephen Rothwell
2009-06-03 9:09 Stephen Rothwell
2008-06-03 8:30 Stephen Rothwell
2008-06-04 11:28 ` Dmitri Vorobiev
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=201006051221.38088.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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