linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Burton <paulburton@kernel.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: paul.burton@mips.com, ralf@linux-mips.org, jhogan@kernel.org,
	chenhc@lemote.com
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: linux-mips@vger.kernel.org
Subject: Re: [PATCH v3] MIPS: Loongson: Make default kernel log buffer size as  128KB for Loongson3
Date: Fri, 01 Nov 2019 16:28:12 -0700	[thread overview]
Message-ID: <5dbcbf8d.1c69fb81.d579.a9f1@mx.google.com> (raw)
In-Reply-To: <1571220180-5478-1-git-send-email-yangtiezhu@loongson.cn>

Hello,

Tiezhu Yang wrote:
> When I update kernel with loongson3_defconfig based on the Loongson 3A3000
> platform, then using dmesg command to show kernel ring buffer, the initial
> kernel messages have disappeared due to the log buffer is too small, it is
> better to change the kernel log buffer size from 16KB to 128KB which is
> enough to save the boot messages.
> 
> Since the default LOG_BUF_SHIFT value is 17, the default kernel log buffer
> size is 128KB, just delete the CONFIG_LOG_BUF_SHIFT line.

Applied to mips-next.

> commit 8a5a49987130
> https://git.kernel.org/mips/c/8a5a49987130
> 
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> Signed-off-by: Paul Burton <paulburton@kernel.org>

Thanks,
    Paul

[ This message was auto-generated; if you believe anything is incorrect
  then please email paulburton@kernel.org to report it. ]

      reply	other threads:[~2019-11-01 23:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16 10:03 [PATCH v3] MIPS: Loongson: Make default kernel log buffer size as 128KB for Loongson3 Tiezhu Yang
2019-11-01 23:28 ` Paul Burton [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=5dbcbf8d.1c69fb81.d579.a9f1@mx.google.com \
    --to=paulburton@kernel.org \
    --cc=chenhc@lemote.com \
    --cc=jhogan@kernel.org \
    --cc=paul.burton@mips.com \
    --cc=ralf@linux-mips.org \
    --cc=yangtiezhu@loongson.cn \
    /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;
as well as URLs for NNTP newsgroup(s).