public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: 01 Apr 2004 05:40:59 -0500	[thread overview]
Message-ID: <1080816043.31353.181.camel@dhcppc4> (raw)

Hi Marcelo, please do a 

	bk pull bk://linux-acpi.bkbits.net/linux-acpi-release-2.4.26

thanks,
-Len

ps. a plain patch is also available here:
ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.4.26/acpi-20040326-2.4.26.diff.gz

This will update the following files:

 arch/i386/kernel/acpi.c      |    4 +++
 arch/i386/kernel/io_apic.c   |    6 ++++-
 arch/x86_64/kernel/io_apic.c |    6 ++++-
 drivers/acpi/bus.c           |    5 ++++
 drivers/acpi/pci_irq.c       |   35 +++++++++++++++++--------------
 include/asm-i386/acpi.h      |    9 -------
 include/asm-i386/system.h    |    5 ----
 7 files changed, 40 insertions(+), 30 deletions(-)

through these ChangeSets:

<len.brown@intel.com> (04/04/01 1.1063.46.95)
   [ACPI] Restore PIC-mode SCI default to Level Trigger (David Shaohua
Li)
   http://bugme.osdl.org/show_bug.cgi?id=2382

<len.brown@intel.com> (04/04/01 1.1063.46.94)
   [ACPI] PCI bridge interrupt fix (David Shaohua Li)
   http://bugzilla.kernel.org/show_bug.cgi?id=2409

<len.brown@intel.com> (04/04/01 1.1063.46.93)
   [ACPI] delete extraneous IRQ->pin mappings below IRQ 16
   http://bugzilla.kernel.org/show_bug.cgi?id=2408

<len.brown@intel.com> (04/03/30 1.1063.46.92)
   [ACPI] allow building ACPI w/ CMPXCHG when CONFIG_M386=y
   http://bugzilla.kernel.org/show_bug.cgi?id=2391





             reply	other threads:[~2004-04-01 10:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 10:40 Len Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-31  8:32 [BKPATCH] ACPI for 2.4 Len Brown
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-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=1080816043.31353.181.camel@dhcppc4 \
    --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