From: Samuel Ortiz <samuel@sortiz.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 19 (nfc)
Date: Tue, 20 Dec 2011 17:39:41 +0100 [thread overview]
Message-ID: <1324399181.5354.0.camel@sortiz-mobl> (raw)
In-Reply-To: <4EEFA21B.5010305@xenotime.net>
Hi Randy,
On Mon, 2011-12-19 at 12:44 -0800, Randy Dunlap wrote:
> On 12/18/2011 11:55 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20111216:
>
>
> (not new today, just not reported earlier)
John applied my fix for this one. It should be fixed now.
Cheers,
Samuel.
next prev parent reply other threads:[~2011-12-20 16:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 7:55 linux-next: Tree for Dec 19 Stephen Rothwell
2011-12-19 20:32 ` linux-next: Tree for Dec 19 (xen) Randy Dunlap
2011-12-19 20:32 ` Randy Dunlap
2011-12-19 20:47 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-12-19 20:38 ` linux-next: Tree for Dec 19 (staging/media/go7007) Randy Dunlap
2011-12-19 20:44 ` linux-next: Tree for Dec 19 (nfc) Randy Dunlap
2011-12-20 16:39 ` Samuel Ortiz [this message]
2011-12-20 20:14 ` Randy Dunlap
2011-12-20 20:14 ` Randy Dunlap
2011-12-21 19:57 ` Randy Dunlap
2011-12-21 19:57 ` Randy Dunlap
2011-12-21 19:02 ` John W. Linville
2011-12-21 20:20 ` Randy Dunlap
[not found] ` <4EF23A1F.60803-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2011-12-21 20:42 ` Samuel Ortiz
2011-12-21 20:42 ` Samuel Ortiz
2011-12-21 21:58 ` Randy Dunlap
2011-12-21 23:35 ` Samuel Ortiz
2011-12-22 1:52 ` Randy Dunlap
2011-12-22 1:03 ` Stephen Rothwell
2011-12-20 1:52 ` linux-next: Tree for Dec 19 Mark Brown
2011-12-20 3:20 ` Stephen Rothwell
2011-12-20 6:39 ` Stephen Rothwell
2011-12-20 11:54 ` Mark Brown
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=1324399181.5354.0.camel@sortiz-mobl \
--to=samuel@sortiz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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.