From: R Cerqueira <acpi4asus-list@cerqueira.org>
To: Timo Hoenig <thoenig@suse.de>
Cc: Karol Kozimor <sziwan@hell.org.pl>,
akpm@osdl.org, "Brown, Len" <len.brown@intel.com>,
acpi4asus-user@lists.sourceforge.net, marekw1977@yahoo.com.au,
linux-acpi@vger.kernel.org
Subject: Re: [Acpi4asus-user] [patch 1/6] asus_acpi: W3000 support
Date: Sat, 01 Jul 2006 23:46:23 +0100 [thread overview]
Message-ID: <1151793983.27214.4.camel@frolic> (raw)
In-Reply-To: <1151765434.30054.9.camel@nouse.suse.de>
On Sat, 2006-07-01 at 16:50 +0200, Timo Hoenig wrote:
> Hi,
>
> On Fri, 2006-06-30 at 21:31 +0200, Karol Kozimor wrote:
>
> > I would really prefer this to be respun and applied *over* the batch
> > of patches I sent you *in mid-January*, as they rework some significant
> > portions of the code this patch touches and it would be a real PITA to
> > respin that batch instead of this little piece here.
>
> Updating ASUS ACPI to 0.30 would be absolutely be adorable.
>
> We have applied the patches for SL 10.1 as well as for SLES 10 and SLED
> 10. My bug count for the driver is zero with regard to those patches.
Since we're talking about applying patches, it would be nice if the W5F
patch I sent to the list back on April 26th could go in as well.
Anything wrong with it?
--
Ricardo Cerqueira
next prev parent reply other threads:[~2006-07-01 22:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 18:10 [patch 1/6] asus_acpi: W3000 support Brown, Len
2006-06-30 19:31 ` Karol Kozimor
2006-07-01 14:50 ` [Acpi4asus-user] " Timo Hoenig
2006-07-01 22:46 ` R Cerqueira [this message]
2006-07-01 23:05 ` Timo Hoenig
2006-07-01 23:35 ` Andrew Morton
2006-07-02 9:46 ` Johannes Engel
2006-07-02 10:35 ` Timo Hoenig
2006-07-02 10:33 ` Timo Hoenig
2006-07-01 23:06 ` Karol Kozimor
-- strict thread matches above, loose matches on Subject: below --
2006-07-01 16:26 Brown, Len
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=1151793983.27214.4.camel@frolic \
--to=acpi4asus-list@cerqueira.org \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=marekw1977@yahoo.com.au \
--cc=sziwan@hell.org.pl \
--cc=thoenig@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.