From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>, Andi Shyti <andi.shyti@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: davinci: add I2C_FUNC_PROTOCOL_MANGLING to feature list
Date: Mon, 5 May 2025 15:10:12 +0200 [thread overview]
Message-ID: <aBi4tE4IQxoh7jYL@gmail.com> (raw)
In-Reply-To: <20250326-i2c-v1-1-82409ebe9f2b@gmail.com>
Hello,
On Wed, Mar 26, 2025 at 03:39:47PM +0100, Marcus Folkesson wrote:
> The driver do support I2C_M_IGNORE_NAK, so add
> I2C_FUNC_PROTOCOL_MANGLING to the feature list.
>
> Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
> ---
Is this patch picked up by any tree?
No confirmation nor showing up in -next makes me wonder.
Thanks,
Marcus Folkesson
next prev parent reply other threads:[~2025-05-05 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 14:39 [PATCH] i2c: davinci: add I2C_FUNC_PROTOCOL_MANGLING to feature list Marcus Folkesson
2025-03-27 5:27 ` Mukesh Kumar Savaliya
2025-05-05 13:10 ` Marcus Folkesson [this message]
2025-05-05 21:15 ` 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=aBi4tE4IQxoh7jYL@gmail.com \
--to=marcus.folkesson@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=brgl@bgdev.pl \
--cc=linux-arm-kernel@lists.infradead.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