From: Dan Williams <dcbw@redhat.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>
Subject: Re: [GIT PATCH] rfkill fixes, set 2
Date: Wed, 16 Jul 2008 12:29:24 -0400 [thread overview]
Message-ID: <1216225764.21973.8.camel@localhost.localdomain> (raw)
In-Reply-To: <1216150327-10904-1-git-send-email-hmh@hmh.eng.br>
On Tue, 2008-07-15 at 16:32 -0300, Henrique de Moraes Holschuh wrote:
> Here is a small set of fixes for rfkill, mostly stuff I noticed while I
> was working on other patches that I will send in for RFC and testing,
> later.
>
> It does include the documentation change requested by Ivo that makes
> rfkill_force_state non-optional where applicable (devices that get
> external state changes).
>
> Shortlog:
>
> Henrique de Moraes Holschuh (4):
> rfkill: document rfkill_force_state as required
> rfkill: fix led-trigger unregister order in error unwind
> rfkill: document the rfkill struct locking
> rfkill: mutex fixes
>
> Please consider for merging for 2.6.26, as they are fixes and not
> enhancements. Ivo, please be specially hard on the last patch, I did
> test it here, but locking is always tricky...
If you do really mean 2.6.26, that's out already so you'd want to send
the patches to stable@ as well. But I assume you mean 2.6.27, right?
Dan
> Patches based on wireless-testing master.
>
next prev parent reply other threads:[~2008-07-16 16:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 19:32 [GIT PATCH] rfkill fixes, set 2 Henrique de Moraes Holschuh
2008-07-15 19:32 ` [PATCH 1/4] rfkill: document rfkill_force_state as required Henrique de Moraes Holschuh
2008-07-19 12:34 ` Ivo van Doorn
2008-07-19 13:42 ` Henrique de Moraes Holschuh
2008-07-15 19:32 ` [PATCH 2/4] rfkill: fix led-trigger unregister order in error unwind Henrique de Moraes Holschuh
2008-07-19 12:35 ` Ivo van Doorn
2008-07-15 19:32 ` [PATCH 3/4] rfkill: document the rfkill struct locking Henrique de Moraes Holschuh
2008-07-19 12:39 ` Ivo van Doorn
2008-07-19 13:43 ` Henrique de Moraes Holschuh
2008-07-15 19:32 ` [PATCH 4/4] rfkill: mutex fixes Henrique de Moraes Holschuh
2008-07-17 4:56 ` Michael Buesch
2008-07-17 11:33 ` drago01
2008-07-17 12:10 ` Henrique de Moraes Holschuh
2008-07-19 12:47 ` Ivo van Doorn
2008-07-19 14:19 ` Henrique de Moraes Holschuh
2008-07-19 14:50 ` Ivo van Doorn
2008-07-19 14:51 ` Ivo van Doorn
2008-07-16 16:29 ` Dan Williams [this message]
2008-07-17 11:54 ` [GIT PATCH] rfkill fixes, set 2 Henrique de Moraes Holschuh
2008-07-17 21:56 ` [PATCH 5/4] rfkill: query EV_SW states when rfkill-input connects to a input device Henrique de Moraes Holschuh
2008-07-19 4:01 ` Dmitry Torokhov
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=1216225764.21973.8.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).