From: Lin Ming <ming.m.lin@intel.com>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: "Moore, Robert" <robert.moore@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: kmemleaks related to ACPI psparse
Date: Wed, 05 Oct 2011 19:54:39 +0800 [thread overview]
Message-ID: <1317815679.3658.10.camel@hp6530s> (raw)
In-Reply-To: <20111004063720.GA13579@sucs.org>
On Tue, 2011-10-04 at 14:37 +0800, Sitsofe Wheeler wrote:
> Hi,
>
> On Fri, Sep 16, 2011 at 10:02:36AM +0100, Sitsofe Wheeler wrote:
> >
> > On Fri, Sep 16, 2011 at 03:29:54PM +0800, Lin Ming wrote:
> > > On Fri, 2011-09-16 at 15:22 +0800, Sitsofe Wheeler wrote:
> > > >
> > > > In 3.1.0-rc5-dirty the following warning appeared in dmesg:
> > >
> > > Please attach the acpidump output.
> >
> > My EeePC 900's acpidump output should be attached as a gz.
>
> This issue hasn't happened since - is it worth ignoring this for now?
Yes.
Thanks for test.
prev parent reply other threads:[~2011-10-05 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 7:22 kmemleaks related to ACPI psparse Sitsofe Wheeler
2011-09-16 7:29 ` Lin Ming
2011-09-16 9:02 ` Sitsofe Wheeler
2011-10-04 6:37 ` Sitsofe Wheeler
2011-10-05 11:54 ` Lin Ming [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=1317815679.3658.10.camel@hp6530s \
--to=ming.m.lin@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=sitsofe@yahoo.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