From: Jonathan Cameron <jic23@kernel.org>
To: David Laight <david.laight.linux@gmail.com>, linux-iio@vger.kernel.org
Cc: "Nicolas Pitre" <nico@fluxnic.net>,
"Borislav Betkov" <bp@alien8.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Thomas Gleinxer" <tglx@linutronix.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
x86@kernel.org, "Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
rodrigo.alencar@analog.com
Subject: Re: [PATCH 0/2] x86: Use "er" asm constriant for add/sub
Date: Tue, 1 Sep 2026 17:51:01 +0100 [thread overview]
Message-ID: <20260901175101.1e059ac8@jic23-huawei> (raw)
In-Reply-To: <20260823233536.30b984ed@jic23-huawei>
On Sun, 23 Aug 2026 23:35:36 +0100
Jonathan Cameron <jonathan.cameron@oss.qualcomm.com> wrote:
> On Mon, 3 Aug 2026 16:39:55 +0100
> David Laight <david.laight.linux@gmail.com> wrote:
>
> > On Mon, 3 Aug 2026 10:49:40 -0400 (EDT)
> > Nicolas Pitre <nico@fluxnic.net> wrote:
> >
> > > On Mon, 3 Aug 2026, David Laight wrote:
> > >
> > > > The x86 instruction set only supports 32bit signed immediate values
> > > > for add/sub.
> > > > Replace the "ir" constraint with "er" to avoid build errors.
> > > >
> > > > Found by a patch that added used mul_u64_add_u64_div_u64() to
> > > > do a rounding divide by 2^32 (perhaps not the best way to do this).
> > > >
> > > > A quick grep only found one other affected file.
> > >
> > > Would be a good idea adding those cases to the test module.
> >
> > They fail to compile so it isn't a big deal.
> >
> David, thanks for sorting this (and all for reviewing)
>
> Seems like everyone is happy. What route is this taking upstream?
>
> I held Rodrigo's driver to avoid the build breakage and would like to
> get it queued up early in next cycle. So not that urgent but nice
> to be able to tick it off the list!
>
Given I have a driver queued up behind this, shall I just take it through
the drivers/iio tree?
I can do an immutable branch just in case anyone else needs it this cycle.
Jonathan
> Thanks,
>
> Jonathan
>
> > David
> >
> > >
> > >
> > > Nicolas
> >
>
parent reply other threads:[~2026-09-01 16:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260823233536.30b984ed@jic23-huawei>]
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=20260901175101.1e059ac8@jic23-huawei \
--to=jic23@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david.laight.linux@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nico@fluxnic.net \
--cc=peterz@infradead.org \
--cc=rodrigo.alencar@analog.com \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@baylibre.com \
--cc=x86@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