From: "Arnd Bergmann" <arnd@arndb.de>
To: "Vineet Gupta" <vineet.gupta@linux.dev>,
"Dinh Nguyen" <dinguyen@kernel.org>,
"schuster.simon@siemens-energy.com"
<schuster.simon@siemens-energy.com>,
"Andrew Morton" <akpm@linux-foundation.org>
Cc: "Sasha Levin" <sashal@kernel.org>,
linux-kernel@vger.kernel.org, "Vineet Gupta" <vgupta@kernel.org>
Subject: Re: [PATCH v3 0/3] lib: Add software mul/div helpers and use them from nios2
Date: Tue, 17 Nov 2026 18:08:51 +0100 [thread overview]
Message-ID: <204a32bb-122d-40b1-88f1-73fd2a6f4b54@app.fastmail.com> (raw)
In-Reply-To: <41664890-337a-402e-895f-376c941d83f2@linux.dev>
On Tue, Nov 17, 2026, at 18:05, Vineet Gupta wrote:
> On 11/16/26 5:19 AM, Dinh Nguyen wrote:
>> On 11/10/26 09:58, Simon Schuster wrote
>>> ---
>> If there are no further comments on this patchset, I can pull it in?
>
> Sorry got busy. I will test this for ARC tonight. Also can this go via
> Arnd's tree - I can post a followup for ARC which uses P1 so everything
> can go together. Or he can a stable tag or branch of yours, whatever works.
Agreed, I think it makes most sense to go through my tree, I can then
also include the openrisc patch on top.
Dinh, if you send me a pull request, I can merge that into the SoC
tree and you can keep the same commits in your own tree in case
you are worried about dependencies. Otherwise I can of course just
apply the patches directly.
Arnd
prev parent reply other threads:[~2026-11-17 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 15:58 Simon Schuster
2026-11-10 15:58 ` [PATCH v3 1/3] lib: extract 32bit mul/div helpers from nios2 into GENERIC_LIB Simon Schuster
2026-11-10 15:58 ` [PATCH v3 2/3] nios2: export __divsi3_table Simon Schuster
2026-11-10 15:58 ` [PATCH v3 3/3] nios2: Drop usage of libgcc in favour of GENERIC_LIB_* Simon Schuster
2026-11-16 13:19 ` [PATCH v3 0/3] lib: Add software mul/div helpers and use them from nios2 Dinh Nguyen
2026-11-17 17:05 ` Vineet Gupta
2026-11-17 17:08 ` 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=204a32bb-122d-40b1-88f1-73fd2a6f4b54@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=dinguyen@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=schuster.simon@siemens-energy.com \
--cc=vgupta@kernel.org \
--cc=vineet.gupta@linux.dev \
/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
all inboxes | Powered by JetHome®