Re: [PATCH] acer-wmi: does not set persistence state byrfkill_init_sw_state

[Florian Mickler]

On Wed, 30 Mar 2011 22:22:32 +0200
Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote:

> On Wed, 2011-03-30 at 22:17 +0200, Florian Mickler wrote:
> > From: Lee, Chun-Yi <joeyli.kernel@xxxxxxxxx>
> > 
> > Acer BIOS keeps devices state when system reboot, but reset to default
> > device states (Wlan on, Bluetooth off, wwan on) if system cold boot.
> > That means BIOS's initial state is not always real persistence.
> > 
> > So, removed rfkill_init_sw_state because it sets initial state to
> > persistence then replicate to other new killswitch when rfkill-input
> > enabled.
> > After removed it, acer-wmi set initial soft-block state after rfkill
> > register, and doesn't allow set_block until rfkill initial finished.
> > 
> > Reference: bko#31002
> > 	https://bugzilla.kernel.org/show_bug.cgi?id=31002
> > 
> > Cc: Carlos Corbacho <carlos@xxxxxxxxxxxxxxxxxxx>
> > Cc: Matthew Garrett <mjg@xxxxxxxxxx>
> > Cc: Dmitry Torokhov <dtor@xxxxxxx>
> > Cc: Corentin Chary <corentincj@xxxxxxxxxx>
> > Cc: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
> > Signed-off-by: Lee, Chun-Yi <jlee@xxxxxxxxxx>
> > Signed-off-by: Matthew Garrett <mjg@xxxxxxxxxx>
> > Tested-by: OldÃÂich JedliÃÂka <oldium.pro@xxxxxxxxx>
> 
> Your mailer messed up the character set, you're advertising
> Content-Type: text/plain; charset=UTF-8
> and then here putting the byte sequence
> \xc3\x85\xc2\x99
> instead of
> \xc5\x99
> 
> for "Å".
> 
> johannes
> 
Dang. That was vim+xterm or git-send-email. 

I did 

git-send-email sha1^..sha1 --to stable --cc lkml --annotate 

and then moved the CC: Old*ich Jedli*ka line via yy and p to the bottom
and changed it to Tested-by:, and added my Signed-off-by: . 

I don't think I can easily fix this up on my side as my xterm sadly 
has some issues with utf8. 
I don't know what's up with that. Maybe font?

Any tipps?
Flo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/