From: Jonathan Cameron <jic23@kernel.org>
To: Maxwell Doose <m32285159@gmail.com>
Cc: Stepan Ionichev <sozdayvek@gmail.com>,
andrea.merello@iit.it, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, hcazarim@yahoo.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: imu: bno055: terminate dev_err() strings with a newline
Date: Fri, 22 May 2026 15:59:48 +0100 [thread overview]
Message-ID: <20260522155948.47c100c5@jic23-huawei> (raw)
In-Reply-To: <CAKqfh0EPXX1zh3ScPCyBWhSq70wL3MpnUW9TV0Btn5LSF2EGuA@mail.gmail.com>
On Wed, 20 May 2026 15:13:41 -0500
Maxwell Doose <m32285159@gmail.com> wrote:
> On Wed, May 20, 2026 at 2:27 PM Stepan Ionichev <sozdayvek@gmail.com> wrote:
> >
> > Two dev_err() calls in bno055_ser_write_reg() and bno055_ser_read_reg()
> > are missing the trailing newline, so the kernel log buffer continues
> > the next message on the same line.
> >
> > Add the missing \n.
> >
> > Signed-off-by: Stepan Ionichev <sozdayvek@gmail.com>
> > ---
> > drivers/iio/imu/bno055/bno055_ser_core.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/iio/imu/bno055/bno055_ser_core.c b/drivers/iio/imu/bno055/bno055_ser_core.c
> > index 48669dabb..733f9112d 100644
> > --- a/drivers/iio/imu/bno055/bno055_ser_core.c
> > +++ b/drivers/iio/imu/bno055/bno055_ser_core.c
> > @@ -288,7 +288,7 @@ static int bno055_ser_write_reg(void *context, const void *_data, size_t count)
> > struct bno055_ser_priv *priv = context;
> >
> > if (count < 2) {
> > - dev_err(&priv->serdev->dev, "Invalid write count %zu", count);
> > + dev_err(&priv->serdev->dev, "Invalid write count %zu\n", count);
> > return -EINVAL;
> > }
> >
> > @@ -306,7 +306,7 @@ static int bno055_ser_read_reg(void *context,
> > struct bno055_ser_priv *priv = context;
> >
> > if (val_size > 128) {
> > - dev_err(&priv->serdev->dev, "Invalid read valsize %zu", val_size);
> > + dev_err(&priv->serdev->dev, "Invalid read valsize %zu\n", val_size);
> > return -EINVAL;
> > }
> >
>
> Sashiko seems fine with it. Also did a quick visual check and looks
> fine (not compiled, but I wouldn't count this as a functional change).
>
> Reviewed-by: Maxwell Doose <m32285159@gmail.com>
Applied.
Thanks,
J
>
> best regards,
> max
>
>
> > --
> > 2.43.0
> >
> >
>
next prev parent reply other threads:[~2026-05-22 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 19:08 Stepan Ionichev
2026-05-20 20:13 ` Maxwell Doose
2026-05-22 14:59 ` Jonathan Cameron [this message]
2026-06-02 22:18 ` Andy Shevchenko
2026-06-02 22:17 ` Andy Shevchenko
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=20260522155948.47c100c5@jic23-huawei \
--to=jic23@kernel.org \
--cc=andrea.merello@iit.it \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=hcazarim@yahoo.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@gmail.com \
--cc=nuno.sa@analog.com \
--cc=sozdayvek@gmail.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 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®