From: Mark Brown <broonie@kernel.org>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
linux-spi@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: Re: [PATCH v3 net-next 1/2] net: dsa: sja1105: send multiple spi_messages instead of using cs_change
Date: Mon, 24 May 2021 09:35:29 +0100 [thread overview]
Message-ID: <20210524083529.GA4318@sirena.org.uk> (raw)
In-Reply-To: <20210520211657.3451036-2-olteanv@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 284 bytes --]
On Fri, May 21, 2021 at 12:16:56AM +0300, Vladimir Oltean wrote:
> The fact of the matter is that spi_max_message_size() has an ambiguous
> meaning if any non-final transfer has cs_change = true.
This is not the case, spi_message_max_size() is a limit on the size of a
spi_message.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-05-24 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 21:16 [PATCH v3 net-next 0/2] Adapt the sja1105 DSA driver to the SPI controller's transfer limits Vladimir Oltean
2021-05-20 21:16 ` [PATCH v3 net-next 1/2] net: dsa: sja1105: send multiple spi_messages instead of using cs_change Vladimir Oltean
2021-05-24 8:35 ` Mark Brown [this message]
2021-05-24 13:02 ` Vladimir Oltean
2021-06-07 17:56 ` Mark Brown
2021-05-20 21:16 ` [PATCH v3 net-next 2/2] net: dsa: sja1105: adapt to a SPI controller with a limited max transfer size Vladimir Oltean
2021-05-21 20:30 ` [PATCH v3 net-next 0/2] Adapt the sja1105 DSA driver to the SPI controller's transfer limits patchwork-bot+netdevbpf
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=20210524083529.GA4318@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).