From: Johannes Berg <johannes@sipsolutions•net>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: "John W. Linville" <linville@tuxdriver•com>,
linux-next@vger•kernel.org, Matthew Garrett <mjg59@srcf•ucam.org>,
Len Brown <lenb@kernel•org>
Subject: Re: linux-next: wireless tree build failure
Date: Wed, 22 Apr 2009 10:59:06 +0200 [thread overview]
Message-ID: <1240390746.17388.64.camel@johannes.local> (raw)
In-Reply-To: <20090422115738.524272c8.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
Hi Stephen,
> drivers/platform/x86/oqo-wmi.c: In function 'oqo_rfkill_init':
> drivers/platform/x86/oqo-wmi.c:767: error: 'struct rfkill' has no member named 'user_claim_unsupported'
>
> Caused by commit bc3e4095713c0bf57c8c9c1e91d93d6654075079 ("rfkill:
> remove user_claim stuff") interacting with commit
> 03919980ad590ad5c5c181d1bd7d58513ad170bc ("platform/x86: Add oqo-wmi
> driver for model 2 OQO backlight and rfkill control") from the acpi tree.
>
> I have reverted commit bc3e4095713c0bf57c8c9c1e91d93d6654075079 for today.
>
> Johannes, maybe you could suggest a patch for the acpi guys?
Fun. Another rfkill problem. It'll get worse -- I have a complete rfkill
rewrite in the pipeline. For this part it's easy, just remove
user_claim_unsupported use from the driver.
Any suggestions on how to handle the other merge problems?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-04-22 8:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 1:57 linux-next: wireless tree build failure Stephen Rothwell
2009-04-22 8:59 ` Johannes Berg [this message]
2009-04-22 13:03 ` Stephen Rothwell
2009-04-22 13:06 ` John W. Linville
2009-04-22 13:33 ` Johannes Berg
2009-04-22 13:36 ` Matthew Garrett
2009-06-03 2:52 ` Stephen Rothwell
2009-06-15 12:21 ` Stephen Rothwell
2009-04-22 13:11 ` Johannes Berg
2009-04-28 3:28 ` Stephen Rothwell
2009-04-28 12:50 ` John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2009-11-09 8:08 Stephen Rothwell
2009-11-09 13:37 ` Bartlomiej Zolnierkiewicz
[not found] <20090505115455.0b147aeb.sfr@canb.auug.org.au>
2009-05-05 2:55 ` John W. Linville
2009-03-23 4:39 Stephen Rothwell
2009-03-23 4:53 ` David Miller
2009-03-23 5:01 ` Yang Hongyang
2009-03-23 4:55 ` David Miller
2009-03-23 5:06 ` Yang Hongyang
2009-03-23 5:48 ` Stephen Rothwell
2009-03-23 7:59 ` David Miller
2009-03-23 8:10 ` Stephen Rothwell
2009-02-27 2:44 Stephen Rothwell
2009-02-12 8:35 Stephen Rothwell
2009-02-12 16:16 ` John W. Linville
2009-02-12 22:07 ` Stephen Rothwell
2009-02-13 18:24 ` Dave
2009-02-13 18:24 ` John W. Linville
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=1240390746.17388.64.camel@johannes.local \
--to=johannes@sipsolutions$(echo .)net \
--cc=lenb@kernel$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linville@tuxdriver$(echo .)com \
--cc=mjg59@srcf$(echo .)ucam.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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