From: Michal Simek <michal.simek@amd.com>
To: Krzysztof Adamski <krzysztof.adamski@nokia.com>,
Raviteja Narayanam <raviteja.narayanam@xilinx.com>
Cc: <linux-i2c@vger.kernel.org>, <michal.simek@xilinx.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <git@xilinx.com>, <marex@denx.de>,
<joe@perches.com>
Subject: Re: [PATCH v2 02/10] i2c: xiic: Add standard mode support for > 255 byte read transfers
Date: Wed, 29 Jun 2022 13:39:09 +0200 [thread overview]
Message-ID: <27c88580-51bb-7813-c29f-b8a3faaaa294@amd.com> (raw)
In-Reply-To: <c8d4faf1-5f0c-4adb-e52a-92d46179ffa4@nokia.com>
Hi,
On 6/29/22 13:02, Krzysztof Adamski wrote:
>
> Hi,
>
> I know this patch is quite old but we need the smbus_block_read
> functionality, which depends on this one, so I would really like this to
> be merged. See my comments below.
Please try this series and let us know if it is working for you or not.
https://lore.kernel.org/all/1656072327-13628-1-git-send-email-manikanta.guntupalli@xilinx.com/
Thanks,
Michal
next prev parent reply other threads:[~2022-06-29 11:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 10:27 [PATCH v2 00/10] i2c: xiic: Add features, bug fixes Raviteja Narayanam
2021-06-26 10:27 ` [PATCH v2 01/10] i2c: xiic: Fix Tx Interrupt path for grouped messages Raviteja Narayanam
2021-06-26 10:27 ` [PATCH v2 02/10] i2c: xiic: Add standard mode support for > 255 byte read transfers Raviteja Narayanam
2022-06-29 11:02 ` Krzysztof Adamski
2022-06-29 11:39 ` Michal Simek [this message]
2022-06-29 12:07 ` Krzysztof Adamski
2021-06-26 10:27 ` [PATCH v2 03/10] i2c: xiic: Switch to Xiic standard mode for i2c-read Raviteja Narayanam
2022-06-29 12:47 ` Krzysztof Adamski
2022-06-29 14:05 ` Marek Vasut
2022-06-29 14:09 ` Krzysztof Adamski
2022-06-29 14:34 ` Marek Vasut
2022-06-30 8:23 ` Datta, Shubhrajyoti
2022-07-01 7:01 ` Krzysztof Adamski
2022-07-04 5:45 ` Datta, Shubhrajyoti
2021-06-26 10:28 ` [PATCH v2 04/10] i2c: xiic: Remove interrupt enable/disable in Rx path Raviteja Narayanam
2021-06-26 10:28 ` [PATCH v2 05/10] dt-bindings: i2c: xiic: Add 'xlnx,axi-iic-2.1' to compatible Raviteja Narayanam
2021-06-26 10:28 ` [PATCH v2 06/10] i2c: xiic: Update compatible with new IP version Raviteja Narayanam
2021-06-26 10:28 ` [PATCH v2 07/10] i2c: xiic: Return value of xiic_reinit Raviteja Narayanam
2021-06-26 10:28 ` [PATCH v2 08/10] i2c: xiic: Fix the type check for xiic_wakeup Raviteja Narayanam
2021-06-26 10:28 ` [PATCH v2 09/10] i2c: xiic: Fix coding style issues Raviteja Narayanam
2021-06-26 10:28 ` [PATCH v2 10/10] i2c: xiic: Add smbus_block_read functionality Raviteja Narayanam
2021-06-28 7:23 ` [PATCH v2 00/10] i2c: xiic: Add features, bug fixes Michal Simek
2021-07-16 16:01 ` Marek Vasut
2021-07-19 10:09 ` Raviteja Narayanam
2021-07-19 18:00 ` Marek Vasut
2021-07-20 14:19 ` Raviteja Narayanam
2021-07-20 21:43 ` Marek Vasut
2021-07-26 5:26 ` Raviteja Narayanam
2021-07-26 13:12 ` Marek Vasut
2021-07-28 10:11 ` Raviteja Narayanam
2021-07-28 18:47 ` Marek Vasut
2022-06-28 7:50 ` Guntupalli, Manikanta
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=27c88580-51bb-7813-c29f-b8a3faaaa294@amd.com \
--to=michal.simek@amd.com \
--cc=git@xilinx.com \
--cc=joe@perches.com \
--cc=krzysztof.adamski@nokia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=michal.simek@xilinx.com \
--cc=raviteja.narayanam@xilinx.com \
/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
all inboxes | Powered by JetHome®