From: "John W. Linville" <linville@tuxdriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Len Brown <lenb@kernel.org>,
linux-next@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: linux-next: wireless tree build failure
Date: Tue, 28 Apr 2009 08:50:00 -0400 [thread overview]
Message-ID: <20090428125000.GA4113@tuxdriver.com> (raw)
In-Reply-To: <20090428132817.5e86b172.sfr@canb.auug.org.au>
On Tue, Apr 28, 2009 at 01:28:17PM +1000, Stephen Rothwell wrote:
> Hi John, Len,
>
> On Wed, 22 Apr 2009 11:57:38 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Today's linux-next build (x86_64 allmodconfig) failed like this:
> >
> > 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.
>
> This is still happening ... is someone going to do something about it?
Sorry, I mostly forgot about it after Matthew asked for that driver
to be dropped...?
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:[~2009-04-28 13:01 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
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 [this message]
-- 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=20090428125000.GA4113@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=lenb@kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mjg59@srcf.ucam.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.