From: Jean Delvare <jdelvare@suse.de>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: Linux I2C <linux-i2c@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 2/2 RFC] eeprom: at24: Tidy at24_read()
Date: Tue, 25 Aug 2020 08:38:19 +0200 [thread overview]
Message-ID: <20200825083819.7478f26e@endymion> (raw)
In-Reply-To: <CAMpxmJUiOjP5oGijw+QQOFj3uQG0fRGPCAFtcUv_=PxTmy4+4Q@mail.gmail.com>
Hi Bartosz,
On Tue, 18 Aug 2020 15:46:36 +0200, Bartosz Golaszewski wrote:
> On Fri, Aug 7, 2020 at 4:19 PM Jean Delvare <jdelvare@suse.de> wrote:
> > The elegant code in at24_read() has the drawback that we now need
> > to make a copy of all parameters to pass them to the post-processing
> > callback function if there is one. Rewrite the loop in such a way that
> > the parameters are not modified, so saving them is no longer needed.
> >
> > Signed-off-by: Jean Delvare <jdelvare@suse.de>
> > Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> > Cc: Arnd Bergmann <arnd@arndb.de>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > ---
> > This has the drawback of creating an asymetry with at24_write(), so
> > I'm not 100% if we want to apply this. If anyone has a better idea,
> > please let me know.
> >
> > drivers/misc/eeprom/at24.c | 13 +++++--------
> > 1 file changed, 5 insertions(+), 8 deletions(-)
> >
> > --- linux-5.7.orig/drivers/misc/eeprom/at24.c 2020-08-07 14:23:39.882191500 +0200
> > +++ linux-5.7/drivers/misc/eeprom/at24.c 2020-08-07 14:28:39.039360687 +0200
> > (...)
> > @@ -449,15 +446,15 @@ static int at24_read(void *priv, unsigne
> > */
> > mutex_lock(&at24->lock);
> >
> > + i = 0;
>
> Hi Jean,
>
> I think doing:
>
> for (i = 0; count; i += ret, count -= ret)
>
> would be even more elegant, don't you think?
Definitely. I'll change the code that way and send v2 of the patch,
thank you for the suggestion.
> Bartosz
>
> > while (count) {
> > - ret = at24_regmap_read(at24, buf, off, count);
> > + ret = at24_regmap_read(at24, buf + i, off + i, count);
> > if (ret < 0) {
> > mutex_unlock(&at24->lock);
> > pm_runtime_put(dev);
> > return ret;
> > }
> > - buf += ret;
> > - off += ret;
> > + i += ret;
> > count -= ret;
> > }
> >
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2020-08-25 6:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 13:00 [PATCH 1/2] eeprom: at24: Add support for the Sony VAIO EEPROMs Jean Delvare
2020-08-07 14:19 ` [PATCH 2/2 RFC] eeprom: at24: Tidy at24_read() Jean Delvare
2020-08-18 13:46 ` Bartosz Golaszewski
2020-08-25 6:38 ` Jean Delvare [this message]
2020-08-12 18:10 ` [PATCH 1/2] eeprom: at24: Add support for the Sony VAIO EEPROMs Bartosz Golaszewski
2020-08-18 13:41 ` Bartosz Golaszewski
2020-08-24 17:03 ` Jean Delvare
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=20200825083819.7478f26e@endymion \
--to=jdelvare@suse.de \
--cc=arnd@arndb.de \
--cc=bgolaszewski@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-i2c@vger.kernel.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