From: Ivo van Doorn <ivdoorn@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Dan Williams <dcbw@redhat.com>,
Philip Langdale <philipl@overt.org>,
LKML <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
toshiba_acpi@memebeam.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling through rfkill
Date: Mon, 28 Jul 2008 22:32:37 +0200 [thread overview]
Message-ID: <200807282232.38076.IvDoorn@gmail.com> (raw)
In-Reply-To: <20080728185233.GB26564@khazad-dum.debian.net>
On Monday 28 July 2008, Henrique de Moraes Holschuh wrote:
> On Mon, 28 Jul 2008, Dan Williams wrote:
> > On Mon, 2008-07-28 at 00:04 -0300, Henrique de Moraes Holschuh wrote:
> > > On Sun, 27 Jul 2008, Philip Langdale wrote:
> > > > Ivo van Doorn wrote:
> > > >> You don't seem to be using rfkill_force_state() which is required to inform the rfkill
> > > >> layer about the state changes.
> > > >
> > > > Hmm? According to rfkill.txt, one can either use force_state() or implement the
> > > > get_state() hook, and I have done the later. If this is not the correct method,
> > > > can you please explain when I should be using force_state?
> > >
> > > There is a bunch of rfkill bug fix patches that was not merged in
> > > wireless-testing yet (which is a pity, it would be really good if they could
> > > go into 2.6.27). One of those patches fixes the docs to make it clear that
> >
> > Lots of wireless people (including John) were at OLS this past week, so
> > it's not entirely surprising that patch merging might have been slow.
>
> That would explain it, yes... Well, I sure hope this means the patches
> still have a non-zero chance of being sent to mainline for 2.6.27 :-) I am
> not up to date on how merges are usually handled in the wireless and net
> subsystems.
The feature window for 2.6.27 closed with the release of 2.6.26, after that
only bugfixes can go in.
Ivo
next prev parent reply other threads:[~2008-07-28 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 18:17 [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling through rfkill Philip Langdale
2008-07-27 20:59 ` Ivo van Doorn
2008-07-27 22:29 ` Philip Langdale
2008-07-28 3:04 ` Henrique de Moraes Holschuh
2008-07-28 11:17 ` Dan Williams
2008-07-28 18:52 ` Henrique de Moraes Holschuh
2008-07-28 20:32 ` Ivo van Doorn [this message]
2008-07-28 14:17 ` Philip Langdale
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=200807282232.38076.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=dcbw@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=philipl@overt.org \
--cc=toshiba_acpi@memebeam.org \
/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).