All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>,
	Srinivas Neeli <srinivas.neeli@amd.com>,
	Michal Simek <michal.simek@amd.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v2 0/2] gpio: xilinx: Replace custom bitmap APIs
Date: Thu, 6 Feb 2025 14:16:44 -0500	[thread overview]
Message-ID: <Z6UKnNyf9cDVSUPF@thinkpad> (raw)
In-Reply-To: <Z6MzExQFcIz9HlkN@smile.fi.intel.com>

On Wed, Feb 05, 2025 at 11:44:51AM +0200, Andy Shevchenko wrote:
> +Cc: Yury
> 
> On Wed, Feb 05, 2025 at 11:31:09AM +0200, Andy Shevchenko wrote:
> > Relatively recently bitmap APIs gain a few new calls which may help
> > to convert the GPIO Xilinx driver to use them and become shorter and
> > nicer. This mini-series does exactly that.
> > 
> > Changelog v2:
> > - fixed a regression in patch 2
> > 
> > Andy Shevchenko (2):
> >   gpio: xilinx: Use better bitmap APIs where appropriate
> >   gpio: xilinx: Replace custom variants of bitmap_read()/bitmap_write()
> 
> Yury, just FYI, after this series, if applied, the bitmap_remap() and
> bitmap_bitremap() may be moved to the NUMA only APIs. Or i.o.w. the
> commit cde3d0f81e67 ("bitmap: Make bitmap_remap() and bitmap_bitremap()
> available to users") may be reverted.

Thanks Andy, I'll keep an eye on it.


  reply	other threads:[~2025-02-06 19:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05  9:31 [PATCH v2 0/2] gpio: xilinx: Replace custom bitmap APIs Andy Shevchenko
2025-02-05  9:31 ` [PATCH v2 1/2] gpio: xilinx: Use better bitmap APIs where appropriate Andy Shevchenko
2025-02-05  9:31 ` [PATCH v2 2/2] gpio: xilinx: Replace custom variants of bitmap_read()/bitmap_write() Andy Shevchenko
2025-02-05  9:44 ` [PATCH v2 0/2] gpio: xilinx: Replace custom bitmap APIs Andy Shevchenko
2025-02-06 19:16   ` Yury Norov [this message]
2025-02-12  9:58 ` Bartosz Golaszewski

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=Z6UKnNyf9cDVSUPF@thinkpad \
    --to=yury.norov@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --cc=shubhrajyoti.datta@amd.com \
    --cc=srinivas.neeli@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.