[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZO4HF51PXuwklAfS@smile.fi.intel.com>
Date: Tue, 29 Aug 2023 17:56:23 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Yury Norov <yury.norov@...il.com>
Cc: Rasmus Villemoes <linux@...musvillemoes.dk>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/12] bitmap: rework bitmap_{bit,}remap()
On Tue, Aug 29, 2023 at 06:50:08AM -0700, Yury Norov wrote:
> On Tue, Aug 29, 2023 at 6:39 AM Andy Shevchenko
> <andriy.shevchenko@...ux.intel.com> wrote:
> > On Tue, Aug 29, 2023 at 09:33:29AM +0200, Rasmus Villemoes wrote:
...
> > I posted one patch to replace these APIs with something else, more particular
> > for GPIO case(s). Have you chance to look at that? With that taking in, I'm
> > fully agree on the above statement (as we lose the user of this complicated
> > thingy which is a niche of the NUMA as you mentioned already).
>
> I saw the code in a comment in some thread but not as a separate patch, and
> AFAIK you said it's a work-in-progress.
The patch itself is self-contained, the only problem it has no users as is.
The work-in-progress for the test cases, but before I continue with that I want
to hear if it's accepted approach.
> Sorry if I missed your submission. Can you please send the patch or point me to
> the previous submission?
>
> Also, if after your change bitmap_remap would become a NUMA-specific, should
> protect it with NUMA guards?
Rasmus' idea was to move that completely out of the bitmap namespace and scope.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists