mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Andrew Morton <akpm@osdl.org>
Cc: romano@dea.icai.upco.es, romanol@upco.es,
	linux-kernel@vger.kernel.org,
	ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: [BKPATCH] ACPI for 2.6.12-rc1
Date: 18 Mar 2005 21:47:10 -0500	[thread overview]
Message-ID: <1111200429.5935.13.camel@d845pe> (raw)
In-Reply-To: <20050318152122.7994965b.akpm@osdl.org>

On Fri, 2005-03-18 at 18:21, Andrew Morton wrote:
> Romano Giannetti <romanol@upco.es> wrote:
> >
> > Could I humble advocating pushing the patch
> >  http://bugme.osdl.org/attachment.cgi?id=4516&action=view ,please?
> It fixed a
> >  very bad regression in hotkey event from 2.6.9...
> 
> It seems to not be in ACPI bk yet.  What bug number is that actually
> attached to?  There seems to be no way to go backwards from the URL.


Yes, this is an important fix, and I'll be pushing
it up to-akpm tonight along with a bucket-full of
other important fixes.  The push to Linus yesterday
was to clear the pipeline for this next batch, which
should hopefully also make 2.6.12.

cheers,
-Len

ps. You can query bugzilla for comments containing string "id=4516"
and you find this is Luming's burst-mode EC patch:
http://bugzilla.kernel.org/show_bug.cgi?id=3851



  reply	other threads:[~2005-03-19  2:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18  6:23 Len Brown
2005-03-18 15:01 ` Romano Giannetti
2005-03-18 23:21   ` Andrew Morton
2005-03-19  2:47     ` Len Brown [this message]
2005-03-19  3:19     ` [ACPI] " Sérgio Monteiro Basto
     [not found]     ` <20050319215239.GA5105@rukbat.dea.icai.upco.es>
2005-03-29  8:13       ` Romano Giannetti
2005-03-30  6:09         ` [ACPI] " Yu, Luming
2005-03-31 14:59           ` Romano Giannetti

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=1111200429.5935.13.camel@d845pe \
    --to=len.brown@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romano@dea.icai.upco.es \
    --cc=romanol@upco.es \
    /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