linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: linux-acpi@vger.kernel.org
Subject: patches on ACPI release branch
Date: Thu, 11 Jan 2007 04:11:41 -0500	[thread overview]
Message-ID: <11685067081383-git-send-email-len.brown@intel.com> (raw)


The messages following this one contain the patches
in the ACPI git tree on the release branch
for 2.6.20-rc4.  Please speak up if you see any
problems with them.

thanks
-Len

             reply	other threads:[~2007-01-11  9:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-11  9:11 Len Brown [this message]
     [not found] ` <3948ec9406f9a60a43d63f23f6f5284db6529b9c.1168506584.git.len.brown@intel.com>
2007-01-11  9:11   ` [PATCH 1/7] ACPI: Altix: ACPI _PRT support Len Brown
     [not found]   ` <723fe2ca82d1ffc80c9d53035babf011f84c65d4.1168506584.git.len.brown@intel.com>
2007-01-11  9:11     ` [PATCH 2/7] ACPI: ec: enable printk on cmdline use Len Brown
     [not found]   ` <5d65131fa8d333d4575e7dfe5a05d3a9fa4a687e.1168506584.git.len.brown@intel.com>
2007-01-11  9:11     ` [PATCH 3/7] ACPI: rename cstate_entry_s to cstate_entry Len Brown
     [not found]   ` <d6637b28ffb38f207015c990e481fde5bba233d7.1168506584.git.len.brown@intel.com>
2007-01-11  9:11     ` [PATCH 4/7] ACPI: delete two spurious ACPI messages Len Brown
     [not found]   ` <1bb67c2582f4271488721001a707124fd0af347e.1168506584.git.len.brown@intel.com>
2007-01-11  9:11     ` [PATCH 5/7] ACPI: schedule obsolete features for deletion Len Brown
     [not found]   ` <8b59a454c421542a51c391f542c80d165f7547a0.1168506584.git.len.brown@intel.com>
2007-01-11  9:11     ` [PATCH 6/7] ACPI: update MAINTAINERS Len Brown
     [not found]   ` <d2fadbbbf0e42b842731da71864f222e7f119461.1168506584.git.len.brown@intel.com>
2007-01-11  9:11     ` [PATCH 7/7] Revert "ACPI: ibm-acpi: make non-generic bay support optional" Len Brown

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=11685067081383-git-send-email-len.brown@intel.com \
    --to=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).