linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: William Breathitt Gray <wbg@kernel.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v1 1/1] gpio: sch: Switch to memory mapped IO accessors
Date: Mon, 15 Apr 2024 16:05:26 +0300	[thread overview]
Message-ID: <Zh0mFrrmrO1zNmoN@smile.fi.intel.com> (raw)
In-Reply-To: <ZhpC3lLD-BHqJEZz@ishi>

On Sat, Apr 13, 2024 at 04:31:26AM -0400, William Breathitt Gray wrote:
> On Wed, Apr 10, 2024 at 10:21:02AM +0300, Andy Shevchenko wrote:
> > Convert driver to use memory mapped IO accessors.
> > 
> > Signed-off-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> 
> Acked-by: William Breathitt Gray <wbg@kernel.org>

Pushed to my review and testing queue, thank you!

> A minor suggestion below, but I find this patch accepted as-is.
> 
> >  static int sch_gpio_probe(struct platform_device *pdev)
> >  {
> > +	struct device *dev = &pdev->dev;
> 
> In general I think this is a good variable to define to simplify all the
> &pdev->dev appearing throughout this callback, but I'd rather have seen
> it as its own patch so we could change all the other uses of &pdev->dev
> at once without distracting from the memory-mapped I/O change of this
> particular patch. Not really necessary, but maybe at some point in the
> future a follow-up patch doing such a cleanup would be nice.

I avoid making unneeded  churn on a line I have updated in this patch.
That's why I introduced the local variable proactively. Yet, I can do
another patch to clean up the driver based on the existence of this var.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-04-15 13:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10  7:21 [PATCH v1 1/1] gpio: sch: Switch to memory mapped IO accessors Andy Shevchenko
2024-04-12  8:35 ` Linus Walleij
2024-04-12 17:47   ` Andy Shevchenko
2024-04-13  8:31 ` William Breathitt Gray
2024-04-15 13:05   ` Andy Shevchenko [this message]
2024-04-16 21:16   ` Bartosz Golaszewski
2024-04-17  8:04     ` Andy Shevchenko
2024-04-17 18:19       ` Bartosz Golaszewski
2024-04-17 20:40         ` Andy Shevchenko
2024-04-17 20:46           ` Bartosz Golaszewski
2024-04-17 20:49             ` 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=Zh0mFrrmrO1zNmoN@smile.fi.intel.com \
    --to=andy.shevchenko@gmail.com \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wbg@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;
as well as URLs for NNTP newsgroup(s).