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: Fri, 5 Dec 2025 20:33:56 +0900 [thread overview]
Message-ID: <aTLDJPD-4TLEuRI9@shikoro> (raw)
In-Reply-To: <zzuyemsikzpbntvmgxm2fu7p4vs7uwkawyd5rd732p5ralx2fg@wnqvjg2mi7vu>
[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]
Hi Andi,
> here is the pull request for this cycle. I was hoping it would be
> more substantial, but I ran into a nasty issue with my gpg setup
> that blocked me from pushing to kernel.org for several weeks. The
> kernel.org helpdesk helped me sort it out, but unfortunately a
> bit too late, so this is all I managed to gather in time.
Things happen. Don't worry about this one...
> I am sorry for the disruption. I will set up a backup solution so
> that I can avoid this problem in the future.
Another tree at gitlab maybe?
> The following changes since commit 7d0a66e4bb9081d75c82ec4957c50034cb0ea449:
>
> Linux 6.18 (2025-11-30 14:42:10 -0800)
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.
I hope you still have the ref of the branch *before* you rebased to
6.18. Please send a pull request for this old one.
And I am quite sure I said it before: Please *do* *not* rebase branches
you have published which are meant to be consumed! Other people (me!)
depend on their stability and history. In very rare cases, sometimes a
commit needs to be modified or deleted. But the base should really stay
the base. If you need a newer one (also rare), merge it.
Not pulled, sorry.
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-05 11:34 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 [this message]
2025-12-05 23:14 ` Andi Shyti
2025-12-07 13:41 ` Wolfram Sang
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=aTLDJPD-4TLEuRI9@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 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.