public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: linux-i2c <linux-i2c@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: i2c-host for v6.18
Date: Sun, 7 Dec 2025 22:41:34 +0900	[thread overview]
Message-ID: <aTWEDvlMo_Mghlim@shikoro> (raw)
In-Reply-To: <5sisddiomyxmkvm744h5luphomyadnenpjk5pf5kemqw7tcok3@qzmbc2cr42vw>

[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]


> > Urgs, but this is highly problematic. I can't pull something based on
> > 6.18. Usually, things are based on -rc1 or something early to show Linus
> > that it has been in -next for a while. He won't pull something that is
> > less than 48 hours in public and so won't I.
> 
> Just a note that I merged the last few patches on Wednesday. So,
> if the 48 hour window applies, we are well within it.

Well, it is not strictly about 48 hours... I just picked the number
because all of the rebased patches were ~2 days old at the time I looked
at them.

> As I mentioned privately, I can split this into two pull requests
> and use the older reference for the earlier patches if that
> helps. To me it feels more like a formality, since those patches
> have already been in -next for a few weeks and were only rebased
> on top of v6.18.

But this is the key point: after rebasing, no one can see how long they
have been in -next. Especially not the person you ask to pull. This
doesn't look trustworthy. If you hadn't rebased, then one can easily see
that most patches have been in -next for weeks. And if then there are
some new patches on top which are simple enough (like adding an ID),
then the whole pull request probably still looks trustworthy.

> But I am happy to do whatever you prefer.

I prefer one pull request using the ref before the 6.18 rebase.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2025-12-07 13:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 23:35 i2c-host for v6.18 Andi Shyti
2025-12-05 11:33 ` Wolfram Sang
2025-12-05 23:14   ` Andi Shyti
2025-12-07 13:41     ` Wolfram Sang [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=aTWEDvlMo_Mghlim@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=andi.shyti@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.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