linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Yury Norov <yury.norov@gmail.com>,
	Alexander Potapenko <glider@google.com>
Cc: <catalin.marinas@arm.com>, <will@kernel.org>, <pcc@google.com>,
	<andreyknvl@gmail.com>, <andriy.shevchenko@linux.intel.com>,
	<linux@rasmusvillemoes.dk>, <alexandru.elisei@arm.com>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <eugenis@google.com>,
	<syednwaris@gmail.com>, <william.gray@linaro.org>,
	"Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [PATCH v12 1/3] lib/bitmap: add bitmap_{read,write}()
Date: Mon, 4 Dec 2023 16:54:47 +0100	[thread overview]
Message-ID: <ee9b60fb-8c79-44d8-8f4b-63db7e34b596@intel.com> (raw)
In-Reply-To: <ZW3gnNbnzpZwtrMa@yury-ThinkPad>

From: Yury Norov <yury.norov@gmail.com>
Date: Mon, 4 Dec 2023 06:22:20 -0800

> On Mon, Dec 04, 2023 at 02:28:09PM +0100, Alexander Potapenko wrote:
>> On Thu, Nov 9, 2023 at 4:11 PM Alexander Potapenko <glider@google.com> wrote:
>>>
>>> From: Syed Nayyar Waris <syednwaris@gmail.com>
>>>
>>> The two new functions allow reading/writing values of length up to
>>> BITS_PER_LONG bits at arbitrary position in the bitmap.
>>>
>>> The code was taken from "bitops: Introduce the for_each_set_clump macro"
>>> by Syed Nayyar Waris with a number of changes and simplifications:
>>>  - instead of using roundup(), which adds an unnecessary dependency
>>>    on <linux/math.h>, we calculate space as BITS_PER_LONG-offset;
>>>  - indentation is reduced by not using else-clauses (suggested by
>>>    checkpatch for bitmap_get_value());
>>>  - bitmap_get_value()/bitmap_set_value() are renamed to bitmap_read()
>>>    and bitmap_write();
>>>  - some redundant computations are omitted.
>>>
>>> Cc: Arnd Bergmann <arnd@arndb.de>
>>> Signed-off-by: Syed Nayyar Waris <syednwaris@gmail.com>
>>> Signed-off-by: William Breathitt Gray <william.gray@linaro.org>
>>> Link: https://lore.kernel.org/lkml/fe12eedf3666f4af5138de0e70b67a07c7f40338.1592224129.git.syednwaris@gmail.com/
>>> Suggested-by: Yury Norov <yury.norov@gmail.com>
>>> Co-developed-by: Alexander Potapenko <glider@google.com>
>>> Signed-off-by: Alexander Potapenko <glider@google.com>
>>> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>>
>> Yury, Andy, do you think anything else is needed for this series?
>> If not, whom should we ask to take it?
> 
> I probably need to revisit it, but generally it looks OK.
> 
> But I can't take new API without having real users. Now that your MTE
> series is delayed, and Alexander's 'ip_tunnel flags' is not moving as
> well, there's non-zero chance to merge dead code.

One of the PFCP developers had a quick vacation, we'll send PFCP with
the ip_tunnel bitmap conversion this week.
I'll tell Jakub he'd need to pull boys' tree :D

> 
> If you want it to be merged, I'd advise you to walk through the kernel
> sources and find good cases where bitmap_read() and bitmap_write() can
> be used. Then append this series with such conversions, and I'll be
> able to move it.
> 
> Thanks,
> Yury

Thanks,
Olek

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-12-04 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 15:11 [PATCH v12 1/3] lib/bitmap: add bitmap_{read,write}() Alexander Potapenko
2023-11-09 15:11 ` [PATCH v12 2/3] lib/test_bitmap: add tests for bitmap_{read,write}() Alexander Potapenko
2023-11-09 15:11 ` [PATCH v12 3/3] lib/test_bitmap: use pr_info() for non-error messages Alexander Potapenko
2023-12-04 13:28 ` [PATCH v12 1/3] lib/bitmap: add bitmap_{read,write}() Alexander Potapenko
2023-12-04 14:22   ` Yury Norov
2023-12-04 15:54     ` Alexander Lobakin [this message]

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=ee9b60fb-8c79-44d8-8f4b-63db7e34b596@intel.com \
    --to=aleksander.lobakin@intel.com \
    --cc=alexandru.elisei@arm.com \
    --cc=andreyknvl@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=eugenis@google.com \
    --cc=glider@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=pcc@google.com \
    --cc=syednwaris@gmail.com \
    --cc=will@kernel.org \
    --cc=william.gray@linaro.org \
    --cc=yury.norov@gmail.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 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).