From: Robert Richter <rric@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-i2c@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Jan Glauber <jan.glauber@gmail.com>,
David Daney <david.daney@cavium.com>,
Wolfram Sang <wsa@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/8] i2c: octeon: check correct size of maximum RECV_LEN packet
Date: Mon, 11 Jan 2021 10:26:18 +0100 [thread overview]
Message-ID: <X/wZupAp0Gr/uDNv@rric.localdomain> (raw)
In-Reply-To: <20210109124314.27466-5-wsa+renesas@sang-engineering.com>
On 09.01.21 13:43:08, Wolfram Sang wrote:
> I2C_SMBUS_BLOCK_MAX defines already the maximum number as defined in the
> SMBus 2.0 specs. No reason to add one to it.
>
> Fixes: 886f6f8337dd ("i2c: octeon: Support I2C_M_RECV_LEN")
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Robert Richter <rric@kernel.org>
next prev parent reply other threads:[~2021-01-11 9:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 12:43 [PATCH 0/8] i2c: improve RECV_LEN documentation & usage Wolfram Sang
2021-01-09 12:43 ` [PATCH 1/8] i2c: refactor documentation of struct i2c_msg Wolfram Sang
2021-01-09 12:43 ` [PATCH 2/8] i2c: remove licence boilerplate from main UAPI header Wolfram Sang
2021-01-09 12:43 ` [PATCH 3/8] i2c: remove licence boilerplate from i2c-dev " Wolfram Sang
2021-01-09 12:43 ` [PATCH 4/8] i2c: octeon: check correct size of maximum RECV_LEN packet Wolfram Sang
2021-01-11 9:26 ` Robert Richter [this message]
2021-01-17 11:27 ` Wolfram Sang
2021-01-09 12:43 ` [PATCH 5/8] i2c: uapi: add macro to describe support for all SMBus transfers Wolfram Sang
2021-01-09 12:43 ` [PATCH 6/8] i2c: algo: bit: use new macro to specifiy capabilities Wolfram Sang
2021-01-09 12:43 ` [PATCH 7/8] i2c: qup: advertise SMBus transfers using RECV_LEN Wolfram Sang
2021-01-09 12:43 ` [PATCH 8/8] i2c: s3c2410: " Wolfram Sang
2021-01-22 9:02 ` [PATCH 0/8] i2c: improve RECV_LEN documentation & usage 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=X/wZupAp0Gr/uDNv@rric.localdomain \
--to=rric@kernel.org \
--cc=david.daney@cavium.com \
--cc=jan.glauber@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@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;
as well as URLs for NNTP newsgroup(s).