[v2,0/1] SPI loopback testing framework updates

Message ID 20230412202009.3750955-1-rohitner@google.com
Headers
Series SPI loopback testing framework updates |

Message

Rohit Ner April 12, 2023, 8:20 p.m. UTC
  ---
V1 Changes : Add module param for iteration length
---
V1->V2 Changes : Fix patch format
---


Rohit Ner (1):
  spi: spi-loopback-test: Add module param for iteration length

 drivers/spi/spi-loopback-test.c | 8 ++++++++
 1 file changed, 8 insertions(+)
  

Comments

Mark Brown April 12, 2023, 8:23 p.m. UTC | #1
On Wed, Apr 12, 2023 at 01:20:08PM -0700, Rohit Ner wrote:
> ---
> V1 Changes : Add module param for iteration length
> ---
> V1->V2 Changes : Fix patch format
> ---

Please don't send cover letters for single patches, if there is anything
that needs saying put it in the changelog of the patch or after the ---
if it's administrative stuff.  This reduces mail volume and ensures that 
any important information is recorded in the changelog rather than being
lost.
  
Mark Brown April 13, 2023, 5:52 p.m. UTC | #2
On Wed, 12 Apr 2023 13:20:08 -0700, Rohit Ner wrote:
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: spi-loopback-test: Add module param for iteration length
      commit: 6d87552c0b86b9677d762002082df5f5b7e3c33f

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark