From: Florian Mickler <florian@mickler.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: stable@kernel.org, linux-kernel@vger.kernel.org, "Lee,
Chun-Yi" <joeyli.kernel@gmail.com>,
Carlos Corbacho <carlos@strangeworlds.co.uk>,
Matthew Garrett <mjg@redhat.com>, Dmitry Torokhov <dtor@mail.ru>,
Corentin Chary <corentincj@iksaif.net>,
"Lee, Chun-Yi" <jlee@novell.com>
Subject: Re: [PATCH] acer-wmi: does not set persistence state by rfkill_init_sw_state
Date: Wed, 30 Mar 2011 23:19:39 +0200 [thread overview]
Message-ID: <20110330231939.70ed40ac@schatten.dmk.lab> (raw)
In-Reply-To: <1301516552.3791.5.camel@jlt3.sipsolutions.net>
On Wed, 30 Mar 2011 22:22:32 +0200
Johannes Berg <johannes@sipsolutions.net> wrote:
> On Wed, 2011-03-30 at 22:17 +0200, Florian Mickler wrote:
> > From: Lee, Chun-Yi <joeyli.kernel@gmail.com>
> >
> > 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@strangeworlds.co.uk>
> > Cc: Matthew Garrett <mjg@redhat.com>
> > Cc: Dmitry Torokhov <dtor@mail.ru>
> > Cc: Corentin Chary <corentincj@iksaif.net>
> > Cc: Johannes Berg <johannes@sipsolutions.net>
> > Signed-off-by: Lee, Chun-Yi <jlee@novell.com>
> > Signed-off-by: Matthew Garrett <mjg@redhat.com>
> > Tested-by: OldÅich JedliÄka <oldium.pro@seznam.cz>
>
> 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
next prev parent reply other threads:[~2011-03-30 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 20:17 Florian Mickler
2011-03-30 20:22 ` Johannes Berg
2011-03-30 21:19 ` Florian Mickler [this message]
2011-03-31 8:30 ` Florian Mickler
2011-03-31 8:49 ` Joey Lee
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=20110330231939.70ed40ac@schatten.dmk.lab \
--to=florian@mickler.org \
--cc=carlos@strangeworlds.co.uk \
--cc=corentincj@iksaif.net \
--cc=dtor@mail.ru \
--cc=jlee@novell.com \
--cc=joeyli.kernel@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=stable@kernel.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
Powered by JetHome