From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
Yosry Ahmed <yosryahmed@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] seq_buf: add seq_buf_do_printk() helper
Date: Sat, 15 Apr 2023 16:04:06 +0900 [thread overview]
Message-ID: <20230415070406.GJ25053@google.com> (raw)
In-Reply-To: <ZDkWR2lq2MZ4r1aG@alley>
On (23/04/14 11:00), Petr Mladek wrote:
> > +void seq_buf_do_printk(struct seq_buf *s, const char *lvl)
> > +{
> > + const char *start, *lf;
> > + int len;
> > +
> > + if (s->size == 0 || s->len == 0)
> > + return;
> > +
> > + seq_buf_terminate(s);
> > +
> > + start = s->buffer;
> > + while ((lf = strchr(start, '\n'))) {
> > + len = lf - start + 1;
> > + printk("%s%.*s", lvl, len, start);
> > + start = ++lf;
> > + }
> > +
> > + /* No trailing LF */
> > + if (start < s->buffer + s->len) {
> > + len = s->buffer + s->len - start;
> > + printk("%s%.*s\n", lvl, len, start);
>
> We know that the string is '\0' terminated, so the last print
> might be easier:
>
> if (start < s->buffer + s->len)
> printk("%s%s\n", lvl, start);
Indeed. Steven, let me know if you'd prefer a v3.
> Anyway, it looks good. With or without this change:
>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
Thanks Petr!
next prev parent reply other threads:[~2023-04-15 7:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 14:38 [PATCHv2] seq_buf: add seq_buf_do_printk() helper Sergey Senozhatsky
2023-04-12 2:46 ` Steven Rostedt
2023-04-12 3:07 ` Sergey Senozhatsky
2023-04-12 3:14 ` Yosry Ahmed
2023-04-14 9:00 ` Petr Mladek
2023-04-15 7:04 ` Sergey Senozhatsky [this message]
2023-04-15 7:43 ` Steven Rostedt
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=20230415070406.GJ25053@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=yosryahmed@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.