public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	linux-i2c <linux-i2c@vger.kernel.org>
Subject: Re: [GIT PULL] i2c-host-fixes for v6.16-rc3
Date: Sat, 21 Jun 2025 22:16:19 +0200	[thread overview]
Message-ID: <aFcTE3XBrkdENtgD@shikoro> (raw)
In-Reply-To: <rf6vyyocdxdtllhsydpbj5pnaptfjlagsqumblg7ysqby3k44k@mmcwop7nfbqg>

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

Hi Andi,

> I've collected one fix for rc3. It’s rebased on top of the latest
> patch you merged from my fixes branch, which in turn is based on
> rc2, so there's no tag for it.

Hmm, rebasing to rc2 was probably a not so good idea. After I pulled
your branch, I now have the Tegra patch from rc1 twice. So, I will
"drop" this pull request and apply the k1 patch myself with your tag.
I think this is the easiest solution...

> I still haven't had the chance to read your naming conversion
> series, last week has been quite packed. If you feel it's ready
> to move forward, please go ahead. Otherwise, if you can give me
> one more week, I'll make sure to review it properly.

Oh, the patch is fine. It is just a scripted search-and-replace,
verified by buildbots. I didn't want a review, just an OK that I am not
interfering with a plan of yours I might be unaware of.

Have a nice weekend, too!

   Wolfram


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

      reply	other threads:[~2025-06-21 20:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20 16:33 [GIT PULL] i2c-host-fixes for v6.16-rc3 Andi Shyti
2025-06-21 20:16 ` 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=aFcTE3XBrkdENtgD@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