lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250517202735.2c589de0@jic23-huawei>
Date: Sat, 17 May 2025 20:27:35 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Ahelenia Ziemiańska
 <nabijaczleweli@...ijaczleweli.xyz>
Cc: Lars-Peter Clausen <lars@...afoo.de>, linux-iio@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] iio: ssp_sensors: optimalize -> optimize

On Thu, 8 May 2025 20:22:02 +0100
Jonathan Cameron <jic23@...nel.org> wrote:

> On Tue, 6 May 2025 21:10:02 +0200
> Ahelenia Ziemiańska <nabijaczleweli@...ijaczleweli.xyz> wrote:
> 
> > Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@...ijaczleweli.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



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ