mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
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 09:55:01 -0700	[thread overview]
Message-ID: <20260908165501.GDaqA95YQKx_IL416d@fat_crate.local> (raw)
In-Reply-To: <aqAtRgouK7DyDlpJ@monoceros>

On Tue, Sep 08, 2026 at 05:49:17PM +0200, Uwe Kleine-König wrote:
> I don't see what you mean. If both the tip tree and the iio tree
> contain the same commit (with or without a tag on it), it doesn't matter
> who created that and when and in which repo it appeared first. The first
> to send it to Linus makes it new for him and all later PRs using it only
> introduce the follow-up commits. So if you pull Jonathan's branch you
> still can send the branch/tag that contains it whenever you like
> independant of when Jonathan sends out his PR.

Yes, I'm going to have to merge that branch into tip now so I'd need the
assurance from Jonathan that this branch is not going to change.

Also, those patches are not tip-conform, but whatever, not that important for
a one-time thing.

What I really don't understand is, why this rush needs to happen now so that
we completely do a one-off on the agreed upon process and we have to do all
this unnecessary gymnastics?

We have plenty of time.

So why do we even have to debate this instead of you folks dropping this and
we merge it through tip and then everything's going the usual way?

When people start merging x86 patches in their trees, when do you think the
process will break down and we'll have to redo branches and go into a crazy
dependency madness?

We're not merging other stuff through tip without an Ack - why can't you
adhere to the process we've all agreed upon?

Yes, this can work now. Is it necessary? Absolutely not because it is
a one-off and will get everyone involved, confused.

So please do not do this in the future. If we don't react to the mail, you can
always ping us on IRC like other folks do.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2026-09-08 16:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03  9:47 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-09-10 18:00   ` [tip: x86/urgent] x86/div64: Fix addition of large constants in mul_u64_add_u64_div_u64() tip-bot2 for David Laight
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-09-23 20:25   ` [tip: x86/asm] x86/local: Support large immediate values in local_(add|sub)() tip-bot2 for David Laight
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
2026-09-08 15:21               ` Borislav Petkov
2026-09-08 15:49                 ` Uwe Kleine-König
2026-09-08 16:55                   ` Borislav Petkov [this message]
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
2026-09-13 23:13                             ` 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=20260908165501.GDaqA95YQKx_IL416d@fat_crate.local \
    --to=bp@alien8.de \
    --cc=akpm@linux-foundation.org \
    --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=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

all inboxes | Powered by JetHome®