From: Paul Mundt <lethal@linux-sh.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
rc@rc0.org.uk, linuxsh-shmedia-dev@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] arch/sh64/Kconfig: doesn't need it's own LOG_BUF_SHIFT
Date: Mon, 8 Aug 2005 11:08:51 +0300 [thread overview]
Message-ID: <20050808080851.GD22245@linux-sh.org> (raw)
In-Reply-To: <20050807215803.GA4006@stusta.de>
[-- Attachment #1: Type: text/plain, Size: 151 bytes --]
On Sun, Aug 07, 2005 at 11:58:03PM +0200, Adrian Bunk wrote:
> The LOG_BUF_SHIFT from lib/Kconfig.debug is sufficient.
>
Yes, looks good, thanks.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-08 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 21:58 [2.6 patch] arch/sh64/Kconfig: doesn't need it's own LOG_BUF_SHIFT Adrian Bunk
2005-08-08 8:08 ` Paul Mundt [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-31 16:26 Adrian Bunk
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=20050808080851.GD22245@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxsh-shmedia-dev@lists.sourceforge.net \
--cc=rc@rc0.org.uk \
/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