public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Josh Hill <joshua.hill@gmail.com>,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	alan@redhat.com, stable@kernel.org,
	Matthew Garrett <mjg@redhat.com>,
	"Zhang, Rui" <rui.zhang@intel.com>,
	linux-acpi@vger.kernel.org
Subject: Re: [2.6.35-rc5] hp-wmi patch missed .35 merge window, requesting addition to next rc
Date: Thu, 23 Sep 2010 10:37:08 +0200	[thread overview]
Message-ID: <201009231037.09097.trenn@suse.de> (raw)
In-Reply-To: <20100921190816.e6ca6a72.akpm@linux-foundation.org>

Hi,

I didn't know about this one.
Can people please add me to CC list on hp-wmi specific bug
reports (for existing and new ones), thanks.

On Wednesday 22 September 2010 04:08:16 Andrew Morton wrote:
> (cc's added)
> The suggestion is that mainline's
> 751ae808f6b29803228609f51aa1ae057f5c576e ("x86 platform drivers: hp-wmi
> Reorder event id processing") be backported into 2.6.35.x to fix the
> post-2.6.32 regression described in
> https://bugzilla.kernel.org/show_bug.cgi?id=15344
Hmm, the bug is still in "open" state, there is no statement that anything
is found yet fixing the issue.

Could you please update the bug report if you verified and are sure
the patch helps.

The patch is a cleanup, has some functional change, but should
do things correctly now. As long as no special case was handled
by always calling:
hp_wmi_get_entry_by_scancode(eventcode);
even it was not a hotkey event, this is a straight forward fix and
if no one else complains, you have my vote for adding this to
stable kernel(s).

about:
> if this patch doesn't make it into .35 my laptop
> will be doing this for its (10.10) entire lifetime.
Isn't Ubuntu following stable 2.6.35.X kernels and you would get this with
an update if it's pushed into stable kernels?
I expect they do follow and there is no need to hurry?

     Thomas

  reply	other threads:[~2010-09-23  8:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 17:23 [2.6.35-rc5] hp-wmi patch missed .35 merge window, requesting addition to next rc Josh Hill
2010-09-22  2:08 ` Andrew Morton
2010-09-23  8:37   ` Thomas Renninger [this message]
2010-09-23  9:25     ` Stefan Bader
2010-09-23 18:00   ` [stable] " Greg KH

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=201009231037.09097.trenn@suse.de \
    --to=trenn@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=alan@redhat.com \
    --cc=joshua.hill@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=rui.zhang@intel.com \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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