From: "Bjørn Mork" <bjorn@mork.no>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
linux-input@vger.kernel.org, chunkeey@googlemail.com,
linville@tuxdriver.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: input0: bad kobj_uevent_env content in show_uevent()
Date: Mon, 03 Sep 2012 09:01:48 +0200 [thread overview]
Message-ID: <87oblnegir.fsf@nemi.mork.no> (raw)
In-Reply-To: <20120903002241.GA20054@kroah.com> (Greg Kroah-Hartman's message of "Sun, 2 Sep 2012 17:22:41 -0700")
Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> On Mon, Sep 03, 2012 at 12:38:31AM +0800, Fengguang Wu wrote:
>
>> It also works reliably for me: 300 boots without a single failure.
>>
>> Tested-by: Fengguang Wu <fengguang.wu@intel.com>
>
> Thanks for figuring this out. I'll apply it for 3.6, but work to get
> rid of CONFIG_HOTPLUG completly for 3.7 as it just causes problems.
OK, do you want me to propose some commit message, or do you prefer to
write something coherent yourself instead? In any case, if you need it
for the oneline hack:
Signed-off-by: Bjørn Mork <bjorn@mork.no>
Bjørn
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-09-03 7:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-02 7:59 input0: bad kobj_uevent_env content in show_uevent() Fengguang Wu
2012-09-02 8:34 ` Fengguang Wu
2012-09-02 8:37 ` Fengguang Wu
2012-09-04 11:46 ` Jean Delvare
2012-09-04 11:54 ` Fengguang Wu
2012-09-04 11:56 ` Bjørn Mork
2012-09-02 13:41 ` Bjørn Mork
2012-09-02 16:38 ` Fengguang Wu
2012-09-03 0:22 ` Greg Kroah-Hartman
2012-09-03 7:01 ` Bjørn Mork [this message]
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=87oblnegir.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=chunkeey@googlemail.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).