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: [GIT PULL] i2c-host for v6.11
Date: Sat, 13 Jul 2024 11:16:15 +0200	[thread overview]
Message-ID: <ZpJF39FFqnJfinQn@shikoro> (raw)
In-Reply-To: <yxymqbpeuhq52w3ie5nl5pkoojjuybaeodqtrd6uhe2rkmfhfb@3dqr6vefsdxh>

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

Hi Andi,

> Not a massive pull request. The majority of changes relate to the
> naming convention updates. Other than that, the holiday period
> has given us some slack in the number of patches queued for this
> pull request.

Thanks, pulled!

> There is still one pending documentation fix required for an
> issue reported by Stephen that I haven't noticed. I need to add
> the documentation check to my workflow. If you don't have the
> bandwidth, I can take care of it.

I applied the fix on top to silence the warning now in linux-next.

> I also have a pending patch for a v2 pull request from Hans de
> Goede ("i2c: i801: Use a different adapter name for IDF
> adapters") that is waiting for precedence.

Can these patches be included, too? I think they are good to go.

http://patchwork.ozlabs.org/project/linux-i2c/list/?series=410673

Or are there issues with them?

> I wish you a great rest of the weekend,

Thank you! Same to you (and everyone else!)

   Wolfram

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

  reply	other threads:[~2024-07-13  9:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-13  8:57 [GIT PULL] i2c-host for v6.11 Andi Shyti
2024-07-13  9:16 ` Wolfram Sang [this message]
2024-07-13  9:17   ` Wolfram Sang
2024-07-13 10:52     ` Andi Shyti
2024-07-13 10:51   ` Andi Shyti

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=ZpJF39FFqnJfinQn@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