From: Jonathan Cameron <jic23@kernel.org>
To: "Ahelenia Ziemiańska" <nabijaczleweli@nabijaczleweli.xyz>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: ssp_sensors: optimalize -> optimize
Date: Sat, 17 May 2025 20:27:35 +0100 [thread overview]
Message-ID: <20250517202735.2c589de0@jic23-huawei> (raw)
In-Reply-To: <20250508202202.38c19704@jic23-huawei>
On Thu, 8 May 2025 20:22:02 +0100
Jonathan Cameron <jic23@kernel.org> wrote:
> On Tue, 6 May 2025 21:10:02 +0200
> Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> wrote:
>
> > Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> > ---
> > drivers/iio/common/ssp_sensors/ssp_spi.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/common/ssp_sensors/ssp_spi.c b/drivers/iio/common/ssp_sensors/ssp_spi.c
> > index f32b04b63ea1..b7f093d7345b 100644
> > --- a/drivers/iio/common/ssp_sensors/ssp_spi.c
> > +++ b/drivers/iio/common/ssp_sensors/ssp_spi.c
> > @@ -104,7 +104,7 @@ static struct ssp_msg *ssp_create_msg(u8 cmd, u16 len, u16 opt, u32 data)
> > /*
> > * It is a bit heavy to do it this way but often the function is used to compose
> > * the message from smaller chunks which are placed on the stack. Often the
> > - * chunks are small so memcpy should be optimalized.
> > + * chunks are small so memcpy should be optimized.
> > */
> > static inline void ssp_fill_buffer(struct ssp_msg *m, unsigned int offset,
> > const void *src, unsigned int len)
>
> Applied.
>
For future reference don't send typo fixes in a series that covers
multiple subsystems. Some sleep deprived maintainer might type
the wrong thing in b4 and pick up the whole series (including
the microblaze one) instead of just the one he should be!
Noticed it when double checking the pull request.
oops
Jonathan
prev parent reply other threads:[~2025-05-17 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f6e465fee5a824a67be1ae7c3bc1b72adcf9471f.1746558529.git.nabijaczleweli@nabijaczleweli.xyz>
2025-05-06 19:10 ` [PATCH 2/2] iio: ssp_sensors: optimalize -> optimize Ahelenia Ziemiańska
2025-05-08 19:22 ` Jonathan Cameron
2025-05-17 19:27 ` Jonathan Cameron [this message]
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=20250517202735.2c589de0@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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