From: Andi Kleen <andi@firstfloor.org>
To: Thomas Renninger <trenn@suse.de>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Andi Kleen <andi@firstfloor.org>,
linux-acpi@vger.kernel.org, "Moore,
Robert" <robert.moore@intel.com>
Subject: Re: [PATCH] ACPI: update debug parameter documentation
Date: Wed, 30 Jul 2008 14:25:44 +0200 [thread overview]
Message-ID: <20080730122544.GH23938@one.firstfloor.org> (raw)
In-Reply-To: <200807301205.24322.trenn@suse.de>
On Wed, Jul 30, 2008 at 12:05:23PM +0200, Thomas Renninger wrote:
> Hi,
>
> the patch should be fine, just a little comment below.
Could you please submit a followup patch with the log_buf_len
suggestion?
-Andi
next prev parent reply other threads:[~2008-07-30 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 21:43 [PATCH] ACPI: update debug parameter documentation Bjorn Helgaas
2008-07-30 10:05 ` Thomas Renninger
2008-07-30 12:25 ` Andi Kleen [this message]
2008-07-30 13:42 ` Thomas Renninger
2008-07-30 14:07 ` Andi Kleen
2008-07-30 17:46 ` Moore, Robert
-- strict thread matches above, loose matches on Subject: below --
2008-10-27 21:40 [patch] " Bjorn Helgaas
2008-10-28 16:13 ` Bjorn Helgaas
2008-10-29 21:28 Bjorn Helgaas
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=20080730122544.GH23938@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-acpi@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=trenn@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox