From: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
To: Vineet Gupta <vgupta@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-snps-arc@lists.infradead.org,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ARC: bitops: Change __fls to return unsigned long
Date: Fri, 27 May 2022 10:37:33 +0200 [thread overview]
Message-ID: <04c05bd5-63c7-bbac-889c-6e9897f7b990@linux.intel.com> (raw)
In-Reply-To: <17bdbca6-8352-50a8-0a3e-49ffe09422a2@kernel.org>
On 5/26/2022 5:42 AM, Vineet Gupta wrote:
> Hi,
>
> On 5/25/22 07:48, Amadeusz Sławiński wrote:
>> As per asm-generic definition and other architectures __fls should
>> return unsigned long.
>>
>> No functional change is expected as return value should fit in unsigned
>> long.
>>
>> Signed-off-by: Amadeusz Sławiński<amadeuszx.slawinski@linux.intel.com>
>
> Applied to for-curr.
>
> Thx,
> -Vineet
And apparently __fls is defined in two places in ARC header and I only
changed one, should I send incremental patch on top of already merged
one or v2?
next prev parent reply other threads:[~2022-05-27 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 14:48 [PATCH 0/2] bitops: __fls adjustments Amadeusz Sławiński
2022-05-25 14:48 ` [PATCH 1/2] ARC: bitops: Change __fls to return unsigned long Amadeusz Sławiński
2022-05-26 3:42 ` Vineet Gupta
2022-05-27 8:37 ` Amadeusz Sławiński [this message]
2022-05-25 14:48 ` [PATCH 2/2] m68k: bitops: Change __fls to return and accept " Amadeusz Sławiński
2022-05-26 10:08 ` [PATCH 0/2] bitops: __fls adjustments Cezary Rojewski
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=04c05bd5-63c7-bbac-889c-6e9897f7b990@linux.intel.com \
--to=amadeuszx.slawinski@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=vgupta@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