From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Daniil Tatianin <d-tatianin@yandex-team.ru>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH v1] printk_ringbuffer: don't needlessly wrap data blocks around
Date: Fri, 5 Sep 2025 12:47:15 +0200 [thread overview]
Message-ID: <aLq_swzD73vOYm-_@pathway.suse.cz> (raw)
In-Reply-To: <84ikhxfejl.fsf@jogness.linutronix.de>
On Fri 2025-09-05 11:19:02, John Ogness wrote:
> FWIW, Aside from inspecting all the related code carefully, I also
> performed various size and boundary tests using small buffers (like 1KB
> and 2KB). I am confortable with these changes.
Great. I wanted to do similar tests ;-)
Daniil, feel free to send new version.
Best Regards,
Petr
next prev parent reply other threads:[~2025-09-05 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 0:10 [PATCH v1] printk_ringbuffer: don't needlessly wrap data blocks around Daniil Tatianin
2025-09-04 7:33 ` John Ogness
2025-09-04 13:58 ` John Ogness
2025-09-04 16:33 ` Petr Mladek
2025-09-04 16:50 ` Daniil Tatianin
2025-09-05 9:13 ` John Ogness
2025-09-05 10:47 ` Petr Mladek [this message]
2025-09-04 14:30 ` 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=aLq_swzD73vOYm-_@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=d-tatianin@yandex-team.ru \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--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