linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Rhyland Klein <rklein@nvidia.com>,
	Anantha Idapalapati <aidapalapati@nvidia.com>
Subject: linux-next: build failure after merge of the wireless tree
Date: Mon, 16 May 2011 12:02:27 +1000	[thread overview]
Message-ID: <20110516120227.27a5a343.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 722 bytes --]

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.

P.S. is the Author information for that commit correct?  It has a From:
line near the bottom of the commit message.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2011-05-16  2:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16  2:02 Stephen Rothwell [this message]
2011-05-16 18:08 ` linux-next: build failure after merge of the wireless tree John W. Linville
  -- strict thread matches above, loose matches on Subject: below --
2011-10-12  2:36 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=20110516120227.27a5a343.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=aidapalapati@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rklein@nvidia.com \
    /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).