Linux SPI subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mark Brown <broonie@kernel.org>
Subject: [GIT PULL] SPI fixes for v6.5-rc1
Date: Sat, 15 Jul 2023 12:53:19 +0100	[thread overview]
Message-ID: <20230715115326.333B8C433C8@smtp.kernel.org> (raw)

The following changes since commit 879a879c216a41f5403d8d3dbc204a48501912bf:

  spi: bcm{63xx,bca}-hsspi: update my email address (2023-07-04 13:54:19 +0100)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v6.5-rc1

for you to fetch changes up to 54ccc8758ef4d29de9e8fdb711c852abbdd4103a:

  mailmap: add entry for Jonas Gorski (2023-07-12 13:11:08 +0100)

----------------------------------------------------------------
spi: Fixes for v6.5

A couple of fairly minor driver specific fixes here, plus a bunch of
maintainership and admin updates.  Nothing too remarkable.

----------------------------------------------------------------
Jaewon Kim (1):
      spi: s3c64xx: clear loopback bit after loopback test

Jonas Gorski (3):
      spi: bcm63xx: fix max prepend length
      MAINTAINERS: add myself for spi-bcm63xx
      mailmap: add entry for Jonas Gorski

Ryan Wanner (1):
      MAINTAINERS: Add myself as a maintainer for Microchip SPI

 .mailmap                  | 1 +
 MAINTAINERS               | 9 ++++++++-
 drivers/spi/spi-bcm63xx.c | 2 +-
 drivers/spi/spi-s3c64xx.c | 2 ++
 4 files changed, 12 insertions(+), 2 deletions(-)

             reply	other threads:[~2023-07-15 11:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-15 11:53 Mark Brown [this message]
2023-07-15 15:57 ` [GIT PULL] SPI fixes for v6.5-rc1 pr-tracker-bot

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=20230715115326.333B8C433C8@smtp.kernel.org \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=torvalds@linux-foundation.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