public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Thonke <iogl64nx@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: robert.moore@intel.com, linux-kernel@vger.kernel.org,
	acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] Re: 2.6.13-rc3-mm3
Date: Fri, 05 Aug 2005 14:00:31 +0200	[thread overview]
Message-ID: <42F354DF.2050402@googlemail.com> (raw)
In-Reply-To: <20050804155513.727a3894.akpm@osdl.org>



Hello Andrew,
> Andrew Morton wrote:
> Michael, I'm assuming that a) this problem remains in those -mm kernels
> which include git-acpi.patch and that b) the problems are not present in
> 2.6.13-rc5 or 2.6.13-rc6, yes?
>   
a.) I don't have any problems in 2.6.13-rc5-git[1-3] and 2.6.13-rc4-mm1 
they are working quite fantastic.
Good work :-)
> So I think we have a bug in git-acpi.patch?
>   
I reverted them and left them in..no problems with kernels I said above.
Again good work :-)
> If that's all correct then can you please test the next -mm (which will
> include git-acpi.patch - the most recent -mm did not) and if the bug's
> still there can you raise a bugzilla.kernel.org entry for it?
>   
I would, but the motherboard is dropped from my hardware test approval. 
Maybe I can get it back to test again
if it helps to solve some acpi issues.
> We seem to have a handful of bug reports against the -mm acpi patch.
>   
Well, I noticed that there are a lots of bugs and I'm willing to find 
search and reproduce them.

> Thanks.
I have to say thanks for the great help/feedback.

Greets and
Best regards

--
_Michael Thonke
IT-Systemintegrator /
System- and Softwareanalyist


      reply	other threads:[~2005-08-05 12:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29 19:42 [ACPI] Re: 2.6.13-rc3-mm3 Moore, Robert
2005-07-30  0:29 ` Michael Thonke
2005-08-04 22:55   ` Andrew Morton
2005-08-05 12:00     ` Michael Thonke [this message]

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=42F354DF.2050402@googlemail.com \
    --to=iogl64nx@gmail.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.moore@intel.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