linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	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 15:33:11 +0200	[thread overview]
Message-ID: <1240407191.21978.17.camel@johannes.local> (raw)
In-Reply-To: <20090422130612.GB3288@tuxdriver.com>

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

On Wed, 2009-04-22 at 09:06 -0400, John W. Linville wrote:
> On Wed, Apr 22, 2009 at 11:03:33PM +1000, Stephen Rothwell wrote:

> > On Wed, 22 Apr 2009 10:59:06 +0200 Johannes Berg <johannes@sipsolutions.net> wrote:
> > >
> > > 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?
> > 
> > Well, the best way (and I know this is simplistic and maybe difficult) is
> > to introduce the new rewrite alongside the old code and then slowly move
> > the clients of the API over.
> 
> Maybe we should put user_claim_unsupported back into struct rfkill
> (and deprecate it) for now?

Sure, we can add the member in the struct back, and just never look at
it since we've removed user claiming anyway.

But that's not the interesting part -- the thing is the rfkill rewrite.
I don't know how to handle that w/o breaking all users. I had hoped to
finish this very soon to be ready early in .31, but I'm still waiting
for Thinkpad and Toshiba conversions (and I forgot who wanted to look at
Toshiba), but if new users are being added in other trees then that's a
problem.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-04-22 13:33 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 [this message]
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=1240407191.21978.17.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=lenb@kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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 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).