From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Jonathan Cameron <jic23@kernel.org>,
David Laight <david.laight.linux@gmail.com>,
linux-iio@vger.kernel.org, Nicolas Pitre <nico@fluxnic.net>,
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>,
rodrigo.alencar@analog.com
Subject: Re: [PATCH 0/2] x86: Use "er" asm constriant for add/sub
Date: Tue, 8 Sep 2026 12:02:42 +0200 [thread overview]
Message-ID: <ap_cLN807bC56OBU@monoceros> (raw)
In-Reply-To: <20260908033216.GAap-BwAmBqoVDUbMK@fat_crate.local>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
On Mon, Sep 07, 2026 at 08:32:16PM -0700, Borislav Petkov wrote:
> On Mon, Sep 07, 2026 at 11:14:44PM +0100, Jonathan Cameron wrote:
> > I went ahead and picked these up on
> > https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git ib-iio-x86-asm-fix-7.3
> > and merged that into the main IIO branch. I want to give plenty of time in next
> > for the driver that was relying on them.
> >
> > Currently this is all in my testing branch but I'll push that out as a non rebasing
> > (ideally) branch a bit later in the week.
>
> No, this is not how this works. x86 changes go through tip and if you need an
> immutable branch, we can give you a tag.
While x86 usually goes through tip and none of the x86 maintainers
commented before Jonathan applied, it got positive feedback from hpa and
peterz a month ago and iio depends on it.
So I suggest to do the practical thing and pull Jonathan's branch into
tip. Technically that doesn't make a difference (apart from maybe branch
vs tag preferences).
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-08 10:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 9:47 [PATCH 0/2] x86: Use "er" asm constriant for add/sub David Laight
2026-08-03 9:47 ` [PATCH 1/2] lib: mul_u64_add_u64_div_u64: Fix addition of large constants David Laight
2026-08-03 10:08 ` H. Peter Anvin
2026-08-03 9:47 ` [PATCH 2/2] x86/local: local_add/local_sub: Support large immediate values David Laight
2026-08-03 10:01 ` Peter Zijlstra
2026-08-03 10:07 ` H. Peter Anvin
2026-08-03 9:59 ` [PATCH 0/2] x86: Use "er" asm constriant for add/sub Peter Zijlstra
2026-08-03 14:49 ` Nicolas Pitre
2026-08-03 15:39 ` David Laight
2026-08-23 22:35 ` Jonathan Cameron
2026-09-01 16:51 ` Jonathan Cameron
2026-09-07 22:14 ` Jonathan Cameron
2026-09-08 3:32 ` Borislav Petkov
2026-09-08 10:02 ` Uwe Kleine-König [this message]
2026-09-08 15:21 ` Borislav Petkov
2026-09-08 15:49 ` Uwe Kleine-König
2026-09-08 16:55 ` Borislav Petkov
2026-09-10 3:20 ` Jonathan Cameron
2026-09-10 3:45 ` Borislav Petkov
2026-09-10 16:09 ` Jonathan Cameron
2026-09-10 18:00 ` Borislav Petkov
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=ap_cLN807bC56OBU@monoceros \
--to=u.kleine-koenig@baylibre.com \
--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=jic23@kernel.org \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.