From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thorsten Blum" <thorsten.blum@toblux.com>
Cc: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
"Xiao W Wang" <xiao.w.wang@intel.com>,
"Palmer Dabbelt" <palmer@rivosinc.com>,
"Charlie Jenkins" <charlie@rivosinc.com>,
"Namhyung Kim" <namhyung@kernel.org>,
"Huacai Chen" <chenhuacai@kernel.org>,
"Youling Tang" <tangyouling@loongson.cn>,
"Tiezhu Yang" <yangtiezhu@loongson.cn>,
"Jinyang He" <hejinyang@loongson.cn>,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bitops: Change function return types from long to int
Date: Fri, 03 May 2024 17:05:39 +0200 [thread overview]
Message-ID: <d59d9b67-3f0c-423c-a76d-74056a8444cb@app.fastmail.com> (raw)
In-Reply-To: <F1D1D3D4-CFB0-47A8-87F0-E1D8A6B5904F@toblux.com>
On Fri, May 3, 2024, at 16:49, Thorsten Blum wrote:
> On 22. Apr 2024, at 17:55, Arnd Bergmann <arnd@arndb.de> wrote:
>>>
>>> I can generally merge such a series with architecture specific
>>> changes through the asm-generic tree, with the appropriate Acks
>>> from the maintainers.
>
> What would it take for this patch (with only generic type changes) to be
> applied?
>
> I did some further investigations and disassembled my test kernel images.
> The patch reduced the number of ARM instructions by 872 with GCC 13 and by
> 2,354 with GCC 14. Other architectures that rely on the generic bitops
> functions will most likely also benefit from this patch.
>
> Tests were done with base commit 9d1ddab261f3e2af7c384dc02238784ce0cf9f98.
Sorry for failing to follow up earlier, I think this is ok, thanks
for your thorough work on this. I've applied it to the asm-generic
tree now.
Arnd
prev parent reply other threads:[~2024-05-03 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 22:38 [PATCH] bitops: Change function return types from long to int Thorsten Blum
2024-04-22 5:24 ` Wang, Xiao W
2024-04-22 9:15 ` Thorsten Blum
2024-04-22 7:44 ` Amadeusz Sławiński
2024-04-22 14:30 ` Thorsten Blum
2024-04-22 15:55 ` Arnd Bergmann
2024-04-23 11:45 ` Thorsten Blum
2024-05-03 14:49 ` Thorsten Blum
2024-05-03 15:05 ` Arnd Bergmann [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=d59d9b67-3f0c-423c-a76d-74056a8444cb@app.fastmail.com \
--to=arnd@arndb.de \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=charlie@rivosinc.com \
--cc=chenhuacai@kernel.org \
--cc=hejinyang@loongson.cn \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=palmer@rivosinc.com \
--cc=tangyouling@loongson.cn \
--cc=thorsten.blum@toblux.com \
--cc=xiao.w.wang@intel.com \
--cc=yangtiezhu@loongson.cn \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).