From: "John W. Linville" <linville@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, netdev@vger.kernel.org,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
kvalo@qca.qualcomm.com
Subject: Re: linux-next: merge of the wireless-next tree into the net-next tree
Date: Wed, 4 Jan 2012 09:02:10 -0500 [thread overview]
Message-ID: <20120104140209.GA2540@tuxdriver.com> (raw)
In-Reply-To: <20120103.202733.1070369898271428121.davem@davemloft.net>
On Tue, Jan 03, 2012 at 08:27:33PM -0500, David Miller wrote:
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Wed, 4 Jan 2012 10:59:47 +1100
>
> > I noticed that the wireless-next tree has been merged into the net-next
> > tree today. Has anything been done about the build failure I reported in
> > the wireless-next a while ago:
> >
> > On 12/22/2011 16:58 +1100, Stephen Rothwell wrote:
> >>
> >> After merging the final tree, today's linux-next build (powerpc
> >> allyesconfig) failed like this:
> >>
> >> drivers/net/wireless/ath/ath6kl/cfg80211.c:27:1: error: expected ')' before 'KBUILD_MODNAME'
> >> drivers/net/wireless/ath/ath6kl/cfg80211.c:27:1: error: 'KBUILD_MODNAME' undeclared here (not in a function)
> >> drivers/net/wireless/ath/ath6kl/cfg80211.c:27:1: error: expected ',' or ';' before string constant
>
> It happens on any platform not just powerpc, John please fix this and
> don't have known unresolved -next build failures in your tree when you
> push to me.
I'm sorry, Dave. I must have let this slip my mind over the holidays
-- maybe this explains why I didn't send the pull request before
Christmas...
Kalle has sent a temporary fix that sidesteps the issue by forcing the
SDIO and USB versions of ath6kl to be built as modules. I'll forward
that on to you today.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2012-01-04 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 23:59 linux-next: merge of the wireless-next tree into the net-next tree Stephen Rothwell
2012-01-03 23:59 ` Stephen Rothwell
2012-01-04 1:27 ` David Miller
2012-01-04 14:02 ` John W. Linville [this message]
2012-01-04 18:32 ` David Miller
2012-01-04 8:02 ` Kalle Valo
2012-01-04 8:02 ` Kalle Valo
2012-01-04 18:24 ` David Miller
2012-01-04 18:50 ` Kalle Valo
2012-01-04 18:50 ` Kalle Valo
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=20120104140209.GA2540@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 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.