From: Len Brown <len.brown@intel.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: [BKPATCH] ACPI for 2.4
Date: 31 Jan 2005 03:32:21 -0500 [thread overview]
Message-ID: <1107160339.18002.44.camel@d845pe> (raw)
Hi Marcelo, please do a
bk pull bk://linux-acpi.bkbits.net/to-marcelo
thanks,
-Len
ps. a plain patch is also available here:
ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.4.29/acpi-20040326-2.4.29.diff.gz
This will update the following files:
arch/i386/kernel/pci-irq.c | 4 ++--
arch/x86_64/kernel/pci-irq.c | 4 ++--
drivers/acpi/pci_irq.c | 4 ++++
drivers/pci/quirks.c | 30 +++++-------------------------
4 files changed, 13 insertions(+), 29 deletions(-)
through these ChangeSets:
<len.brown@intel.com> (05/01/26 1.1499.5.2)
[ACPI] via interrupt quirk fix from 2.6
http://bugzilla.kernel.org/show_bug.cgi?id=3319
Signed-off-by: David Shaohua Li <shaohua.li@intel.com>
Signed-off-by: Len Brown <len.brown@intel.com.
next reply other threads:[~2005-01-31 8:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 8:32 Len Brown [this message]
2005-02-01 1:33 ` [ACPI] [BKPATCH] ACPI for 2.4 Sergio Monteiro Basto
-- strict thread matches above, loose matches on Subject: below --
2004-11-23 6:34 Len Brown
2004-11-16 19:26 Len Brown
2004-11-09 8:17 Len Brown
2004-10-28 9:33 Len Brown
2004-06-18 7:32 Len Brown
2004-05-20 6:14 Len Brown
2004-05-06 22:28 Len Brown
2004-04-01 12:24 O.Sezer
2004-04-01 12:57 ` O.Sezer
2004-04-01 10:40 Len Brown
2004-03-27 0:53 Len Brown
2004-03-23 10:43 Len Brown
2004-03-14 6:01 Len Brown
2004-03-06 6:32 Len Brown
2004-02-25 10:01 Len Brown
2004-02-07 9:10 Len Brown
2004-02-08 8:20 ` Willy Tarreau
2004-02-08 9:08 ` Willy Tarreau
2003-11-18 20:58 Len Brown
2003-11-20 11:16 ` Len Brown
2003-11-21 17:49 ` Willy Tarreau
2003-11-21 18:46 ` Willy Tarreau
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=1107160339.18002.44.camel@d845pe \
--to=len.brown@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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