From: "John W. Linville" <linville@tuxdriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Rhyland Klein <rklein@nvidia.com>,
Anantha Idapalapati <aidapalapati@nvidia.com>
Subject: Re: linux-next: build failure after merge of the wireless tree
Date: Mon, 16 May 2011 14:08:17 -0400 [thread overview]
Message-ID: <20110516180817.GC6551@tuxdriver.com> (raw)
In-Reply-To: <20110516120227.27a5a343.sfr@canb.auug.org.au>
On Mon, May 16, 2011 at 12:02:27PM +1000, Stephen Rothwell wrote:
> Hi John,
>
> After merging the wireless tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: "clk_get" [net/rfkill/rfkill-gpio.ko] undefined!
> ERROR: "clk_enable" [net/rfkill/rfkill-gpio.ko] undefined!
> ERROR: "clk_put" [net/rfkill/rfkill-gpio.ko] undefined!
> ERROR: "clk_disable" [net/rfkill/rfkill-gpio.ko] undefined!
>
> Caused by commit 165d625850e8 ("net: rfkill: add generic gpio rfkill
> driver").
>
> I have used the wireless tree from next-20110513 for today.
Yeah, I think I'm going to drop this for now until we can sort this out.
> P.S. is the Author information for that commit correct? It has a From:
> line near the bottom of the commit message.
That does look strange. I'll ask Rhyland to make that more clear.
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:[~2011-05-16 18:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 2:02 linux-next: build failure after merge of the wireless tree Stephen Rothwell
2011-05-16 18:08 ` John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-12 2:36 Stephen Rothwell
2011-10-12 2:36 ` Stephen Rothwell
2011-06-23 3:03 Stephen Rothwell
2011-06-23 3:03 ` Stephen Rothwell
2011-06-23 3:46 ` David Miller
2011-06-28 18:11 ` Gustavo F. Padovan
2010-06-23 2:51 Stephen Rothwell
2010-06-23 14:57 ` John W. Linville
2010-03-10 3:36 Stephen Rothwell
2010-03-10 5:53 ` Juuso Oikarinen
2010-03-10 11:19 ` Luciano Coelho
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=20110516180817.GC6551@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=aidapalapati@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rklein@nvidia.com \
--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.