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>,
"linville@tuxdriver.com" <linville@tuxdriver.com>
Subject: Re: linux-next: Tree for Dec 19 (nfc)
Date: Thu, 22 Dec 2011 00:35:22 +0100 [thread overview]
Message-ID: <1324510522.5354.5.camel@sortiz-mobl> (raw)
In-Reply-To: <4EF2569D.1070806@xenotime.net>
On Wed, 2011-12-21 at 13:58 -0800, Randy Dunlap wrote:
> On 12/21/2011 12:42 PM, Samuel Ortiz wrote:
> > Hi Randy,
> >
> > On Wed, 2011-12-21 at 11:57 -0800, Randy Dunlap wrote:
> >> On 12/20/2011 08:39 AM, Samuel Ortiz wrote:
> >>> 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.
> >>
> >> Hi Samuel,
> >>
> >> Is this supposed to be fixed in linux-next?
> >> It still fails today (linux-next 20111221).
> > Do you have a .config for me to look at ?
>
> Sure, one of several that failed is attached.
Thanks, I just tried this one and it seems to work fine. What's your
toolchain ?
I'm using: gcc version 4.6.2 (Debian 4.6.2-4)
Cheers,
Samuel.
next prev parent reply other threads:[~2011-12-21 23:30 UTC|newest]
Thread overview: 19+ 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: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
2011-12-20 20:14 ` Randy Dunlap
2011-12-21 19:57 ` Randy Dunlap
2011-12-21 19:02 ` John W. Linville
2011-12-21 20:20 ` Randy Dunlap
2011-12-21 20:42 ` Samuel Ortiz
2011-12-21 21:58 ` Randy Dunlap
2011-12-21 23:35 ` Samuel Ortiz [this message]
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=1324510522.5354.5.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=linville@tuxdriver.com \
--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 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).