From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Sunil Naidu" <akula2.shark@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Frederik Deweerdt" <deweerdt@free.fr>,
"Alistair John Strachan" <s0348365@sms.ed.ac.uk>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: Linux 2.6.21 - something wrong with dmesg.
Date: Fri, 27 Apr 2007 08:55:00 -0700 [thread overview]
Message-ID: <20070427085500.1c4b267c.randy.dunlap@oracle.com> (raw)
In-Reply-To: <8355959a0704270731k97da30anf1c010f7ae3dc18c@mail.gmail.com>
On Fri, 27 Apr 2007 20:01:37 +0530 Sunil Naidu wrote:
> On 4/26/07, Alistair John Strachan <s0348365@sms.ed.ac.uk> wrote:
> > >
> > > Don't you need to increase CONFIG_LOG_BUF_SHIFT ?
>
> Yep, I need to. But, have to enable the Kernel Debug (DEBUG_KERNEL) to
> increase the value from default 14 value to 15/16. I feel that this
> might increase the kernel size?
>
> Ummm, is it possible to move CONFIG_LOG_BUF_SHIFT under the General
> Setup area? (say, down the Kernel .config support - IKCONFIG).
>
> Comments pl?
Yes, that would be OK. Can you submit a patch for that?
> > (Also, does Andrew really need to be CCed twice?)
>
> I agree with you - my apologies to Andrew ;-) (shall bug him @ linux
> foundation only)
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-04-27 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 12:14 Sunil Naidu
2007-04-26 13:03 ` Frederik Deweerdt
2007-04-26 14:35 ` Alistair John Strachan
2007-04-27 14:31 ` Sunil Naidu
2007-04-27 15:39 ` Alistair John Strachan
2007-04-27 15:55 ` Randy Dunlap [this message]
2007-04-27 19:53 ` [PATCH] Move LOG_BUF_SHIFT to a more sensible place Alistair John Strachan
2007-04-27 21:37 ` Randy Dunlap
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=20070427085500.1c4b267c.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=akula2.shark@gmail.com \
--cc=deweerdt@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.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
all inboxes | Powered by JetHome®