From: "feng.zhou" <realsummitzhou@gmail.com>
To: john.ogness@linutronix.de
Cc: linux-kernel@vger.kernel.org, pmladek@suse.com,
realsummitzhou@gmail.com, rostedt@goodmis.org,
senozhatsky@chromium.org
Subject: [RESEND] Re: [PATCH] printk: Fix _DESCS_COUNT type for 64-bit systems
Date: Mon, 2 Feb 2026 23:07:50 +0800 [thread overview]
Message-ID: <20260202150750.10985-1-realsummitzhou@gmail.com> (raw)
In-Reply-To: <87o6m7fk4c.fsf@jogness.linutronix.de>
Hi John and maintainers,
(Resending to the list - apologies for the initial off-list reply)
On Mon, Feb 2, 2026, John Ogness wrote:
> This is important to us as well! And we really do want those
> wrap-arounds to happen early.
> Your v1 is certainly OK as-is. I just want to do some more investigating
> and testing. With your patch it will be the first time we experience
> descriptor ID wraps.
>
> As to the other U->UL conversion, I really have no preference. Let's
> just wait a bit in case Petr wants to comment.
Thank you for the feedback! I understand v1 is acceptable and you're doing
additional testing. I'll wait for Petr's comments and your investigation
results before any further action.
For the record, here's a summary of our off-list discussion:
1. Early wrap-around testing is important for the printk_ringbuffer design
itself, not just for matching documentation.
2. John noted this is interesting because it will be the first time descriptor
ID wraps are actually exercised in practice.
3. There's a similar issue with the text buffer array size definition using 1U,
but we agreed to wait for broader maintainer input on whether to address it
in the same patch or separately.
I apologize for not using "Reply All" initially - I'm still learning the
kernel development process. I'll make sure all future communications stay
on-list.
Thanks again for your patience and guidance!
Best regards,
Zhou
next prev parent reply other threads:[~2026-02-02 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 9:41 feng.zhou
2026-02-02 11:41 ` John Ogness
2026-02-02 15:07 ` feng.zhou [this message]
2026-02-03 17:24 ` [RESEND] " Petr Mladek
2026-03-03 16:52 ` Petr Mladek
2026-03-10 16:37 ` Petr Mladek
2026-03-10 21:40 ` John Ogness
2026-03-12 9:02 ` 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=20260202150750.10985-1-realsummitzhou@gmail.com \
--to=realsummitzhou@gmail.com \
--cc=john.ogness@linutronix.de \
--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
all inboxes | Powered by JetHome®