From: "John W. Linville" <linville@tuxdriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Miller <davem@davemloft.net>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2008-08-04
Date: Tue, 5 Aug 2008 10:05:17 -0400 [thread overview]
Message-ID: <20080805140517.GA7819@tuxdriver.com> (raw)
In-Reply-To: <20080805232839.95235680.sfr@canb.auug.org.au>
On Tue, Aug 05, 2008 at 11:28:39PM +1000, Stephen Rothwell wrote:
> Hi David,
>
> On Tue, 05 Aug 2008 01:28:14 -0700 (PDT) David Miller
> <davem@davemloft.net> wrote:
> >
> > From: "John W. Linville" <linville@tuxdriver.com>
> > Date: Mon, 4 Aug 2008 22:17:10 -0400
> >
> > > On Mon, Aug 04, 2008 at 03:01:47PM -0700, David Miller wrote:
> > > > I'm holding off on this pull until the list.h changes get so me lkml
> > > > ACKs.
> > >
> > > Sure, np. I created a "no-ath9k" branch in case you are feeling
> > > frisky -- it is the same except for omitting the list.h changes,
> > > the ath5k pci table change, and the new ath9k driver.
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git no-ath9k
> > >
> > > Hth!
> >
> > Due to the powerpc build failures the list.h stuff causes, I'm going
> ^^^^^^^
> It was a sparc64 defconfig that failed due to the list.h changes. The
> powerpc build only failed when I added an include of <linux/bug.h> to
> list.h.
>
> The powerpc compiler got an internal error trying to compile the ath9k
> code - but I don't know if there is anything we can to do to the source
> to work around that.
FWIW I fixed-up the wireless-2.6 tree to reflect what davem pulled -- a
noop, but at least those patches shouldn't pollute -next tomorrow. :-)
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-08-05 14:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 19:37 pull request: wireless-2.6 2008-08-04 John W. Linville
2008-08-04 20:38 ` Marcel Holtmann
2008-08-04 20:45 ` John W. Linville
2008-08-04 21:42 ` Marcel Holtmann
2008-08-04 21:54 ` John W. Linville
2008-08-04 22:37 ` Marcel Holtmann
2008-08-04 22:45 ` Luis R. Rodriguez
2008-08-04 23:38 ` Justin Mattock
2008-08-04 21:58 ` David Miller
2008-08-04 22:01 ` David Miller
[not found] ` <20080804.150147.78586437.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-08-05 2:17 ` John W. Linville
2008-08-05 3:04 ` Pavel Roskin
2008-08-05 8:28 ` David Miller
[not found] ` <20080805.012814.215633850.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-08-05 13:28 ` Stephen Rothwell
2008-08-05 14:05 ` John W. Linville [this message]
2008-08-05 15:30 ` 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=20080805140517.GA7819@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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 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).