From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>, Xiang Gao <gxxa03070307@gmail.com>
Cc: rostedt@goodmis.org, senozhatsky@chromium.org,
linux-kernel@vger.kernel.org, fengqi@xiaomi.com,
xiaoa <gaoxiang19870307@163.com>
Subject: Re: [PATCH] printk: Increase PRINTK_PREFIX_MAX and the buf size in print_caller.
Date: Wed, 29 May 2024 08:39:25 +0206 [thread overview]
Message-ID: <87y17tktze.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <ZlSewPTyQ-jMpW5n@pathway.suse.cz>
On 2024-05-27, Petr Mladek <pmladek@suse.com> wrote:
> If you need to modify the code to add the extra info, you could also
> modify the buffer size.
Exactly this. Your out-of-tree patch to add extra info should also make
the necessary changes to the buffer sizes. It is your out-of-tree patch
that is broken, not mainline Linux.
John Ogness
next prev parent reply other threads:[~2024-05-29 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 9:19 [PATCH] printk: Increase PRINTK_PREFIX_MAX and the buf size in print_caller Xiang Gao
2024-05-27 14:54 ` Petr Mladek
2024-05-29 6:33 ` John Ogness [this message]
[not found] ` <1717404421510.qmo40jy5kubcunlrdknzajsf@android.mail.163.com>
2024-06-03 12:42 ` Petr Mladek
2024-06-03 13:15 ` gxxa03070307
2024-06-03 14:59 ` Petr Mladek
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=87y17tktze.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=fengqi@xiaomi.com \
--cc=gaoxiang19870307@163.com \
--cc=gxxa03070307@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
/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