netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <olteanv@gmail.com>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
	f.fainelli@gmail.com, andrew@lunn.ch, vivien.didelot@gmail.com,
	broonie@kernel.org, linux-spi@vger.kernel.org,
	linux@roeck-us.net, vladimir.oltean@nxp.com
Subject: Re: [PATCH v3 net-next 0/2] Adapt the sja1105 DSA driver to the SPI controller's transfer limits
Date: Fri, 21 May 2021 20:30:10 +0000	[thread overview]
Message-ID: <162162901049.11427.12413955245468287025.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210520211657.3451036-1-olteanv@gmail.com>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Fri, 21 May 2021 00:16:55 +0300 you wrote:
> From: Vladimir Oltean <vladimir.oltean@nxp.com>
> 
> This series changes the SPI transfer procedure in sja1105 to take into
> consideration the buffer size limitations that the SPI controller driver
> might have.
> 
> Changes in v3:
> - Avoid a signed vs unsigned issue in the interpretation of SIZE_MAX.
> - Move the max transfer length checks to probe time, since nothing will
>   change dynamically.
> 
> [...]

Here is the summary with links:
  - [v3,net-next,1/2] net: dsa: sja1105: send multiple spi_messages instead of using cs_change
    https://git.kernel.org/netdev/net-next/c/ca021f0dd851
  - [v3,net-next,2/2] net: dsa: sja1105: adapt to a SPI controller with a limited max transfer size
    https://git.kernel.org/netdev/net-next/c/718bad0e4da9

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-05-21 20:30 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
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 ` patchwork-bot+netdevbpf [this message]

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=162162901049.11427.12413955245468287025.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=broonie@kernel.org \
    --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).