public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Rich Townsend <rhdt-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
To: "Hendrik Jürgens" <hjuerg-ULHALamj7Vx/+Jgy1241yg@public.gmane.org>
Cc: ACPI mailing list
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: sbs-linux acpi-ec-nospinlock patch for 2.6.11
Date: Sun, 06 Mar 2005 13:32:15 -0500	[thread overview]
Message-ID: <422B4CAF.9070401@bartol.udel.edu> (raw)
In-Reply-To: <422AC893.7070304-ULHALamj7Vx/+Jgy1241yg@public.gmane.org>

Hendrik Jürgens wrote:
> Hi!
> 
> is the acpi-ec-nospinlock patch for the new 2.6.11 anywhere on the net?
> the patch for the 2.6.10 does not work for 2.6.11 =/
> 
> Bye
> Hendrik
> 

I'll be fixing this in the latest release of the SBS stuff -- sometime 
over the next few days.

cheers,

Rich


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click

  parent reply	other threads:[~2005-03-06 18:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-06  9:08 sbs-linux acpi-ec-nospinlock patch for 2.6.11 Hendrik Jürgens
     [not found] ` <422AC893.7070304-ULHALamj7Vx/+Jgy1241yg@public.gmane.org>
2005-03-06 18:32   ` Rich Townsend [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-11  5:48 Yu, Luming
2005-03-11 16:37 ` Rich Townsend
     [not found]   ` <4231C946.4090301-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
2005-03-11 16:55     ` Rich Townsend
     [not found]       ` <4231CD8E.5080105-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
2005-03-11 17:54         ` Stefan Seyfried

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=422B4CAF.9070401@bartol.udel.edu \
    --to=rhdt-obnux95toyn10jlvftc4ga@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=hjuerg-ULHALamj7Vx/+Jgy1241yg@public.gmane.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