[00/12,net-next] qca_spi: collection of improvements

Message

Stefan Wahren Dec. 14, 2023, 3:09 p.m. UTC

This series contains a wild collection of improvements for the
qca_spi driver. This is a follow-up series to the recent bugfixes.

Stefan Wahren (12):
  qca_spi: Improve SPI thread creation
  qca_spi: Improve SPI IRQ handling
  qca_spi: Avoid skb_copy_expand in TX path
  qca_7k_common: Drop unnecessary function description
  qca_7k_common: Drop unused len from qcafrm_handle
  qca_spi: Add QCASPI prefix to ring defines
  qca_spi: Introduce QCASPI_RX_MAX_FRAMES
  qca_spi: Improve calculation of RX buffer size
  qca_spi: Log expected signature in error case
  qca_spi: Adjust log of SPI_REG_RDBUF_BYTE_AVA
  qca_7k: Replace BSD boilerplate with SPDX
  qca_7k: Replace old mail address

 drivers/net/ethernet/qualcomm/qca_7k.c        | 17 +---
 drivers/net/ethernet/qualcomm/qca_7k.h        | 16 +---
 drivers/net/ethernet/qualcomm/qca_7k_common.c | 17 +---
 drivers/net/ethernet/qualcomm/qca_7k_common.h | 29 +------
 drivers/net/ethernet/qualcomm/qca_debug.c     | 21 +----
 drivers/net/ethernet/qualcomm/qca_debug.h     | 15 +---
 drivers/net/ethernet/qualcomm/qca_spi.c       | 86 +++++++++----------
 drivers/net/ethernet/qualcomm/qca_spi.h       | 22 ++---
 drivers/net/ethernet/qualcomm/qca_uart.c      | 17 +---
 9 files changed, 57 insertions(+), 183 deletions(-)

--
2.34.1

Comments

Jakub Kicinski Dec. 16, 2023, 2:25 a.m. UTC | #1

On Thu, 14 Dec 2023 16:09:32 +0100 Stefan Wahren wrote:
> This series contains a wild collection of improvements for the
> qca_spi driver. This is a follow-up series to the recent bugfixes.

The fixes are now in net-next, and looks like this series
no longer applied, please rebase & repost.

Stefan Wahren Dec. 16, 2023, 9:26 a.m. UTC | #2

Hi Jakub,

Am 16.12.23 um 03:25 schrieb Jakub Kicinski:
> On Thu, 14 Dec 2023 16:09:32 +0100 Stefan Wahren wrote:
>> This series contains a wild collection of improvements for the
>> qca_spi driver. This is a follow-up series to the recent bugfixes.
> The fixes are now in net-next, and looks like this series
> no longer applied, please rebase & repost.
let me explain. This series shouldn't replace the already applied
bugfixes. Before i submitted the bugfix patches, i prepared all these
patches. Since the bugfixes had a much higher prio, i decided to split
my patches into a bugfix and improvement series. The bugfixes has been
applied and this series is the improvement part which based on current
net-next including the bugfix series. Sorry for not making this clear.
Patch 1 & 2 in this series is the initially intended rework, which is
also considered valuable by Paolo.

Jakub Kicinski Dec. 18, 2023, 10:17 p.m. UTC | #3

On Sat, 16 Dec 2023 10:26:17 +0100 Stefan Wahren wrote:
> let me explain. This series shouldn't replace the already applied
> bugfixes. Before i submitted the bugfix patches, i prepared all these
> patches. Since the bugfixes had a much higher prio, i decided to split
> my patches into a bugfix and improvement series. The bugfixes has been
> applied and this series is the improvement part which based on current
> net-next including the bugfix series. Sorry for not making this clear.

It may be that you based this series on a tree which had the fixes
but the build bot got to it before the fixes propagated to net-next.
They have propagated now, please repost.