From: Artem Bityutskiy <dedekind@infradead.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] [PATCH] Kconfig: enlarge printk buffer size limit
Date: Wed, 07 Mar 2007 13:33:48 +0200 [thread overview]
Message-ID: <1173267228.3886.0.camel@sauron> (raw)
In-Reply-To: <20070302091113.1920ca0f.randy.dunlap@oracle.com>
On Fri, 2007-03-02 at 09:11 -0800, Randy Dunlap wrote:
> That's simple enough, but you could also just add
> log_buf_len=huge_number
Yeah, thanks for the tip, although the Kconfig change would not hurt as
well.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2007-03-07 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 13:27 [RFC] [PATCH] Kconfig: enlarge printk buffer size limit Artem Bityutskiy
2007-03-02 17:11 ` Randy Dunlap
2007-03-07 11:33 ` Artem Bityutskiy [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=1173267228.3886.0.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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