All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Mark Brown <broonie@kernel.org>,
	linux-spi@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 0/4] spi: Various Cleanups
Date: Thu,  7 Oct 2021 22:37:21 +0100	[thread overview]
Message-ID: <163364264937.649954.11489762989707343828.b4-ty@kernel.org> (raw)
In-Reply-To: <20211007121415.2401638-1-u.kleine-koenig@pengutronix.de>

On Thu, 7 Oct 2021 14:14:11 +0200, Uwe Kleine-König wrote:
> while trying to understand how the spi framework makes use of the core
> device driver stuff (to fix a deadlock) I found these simplifications
> and improvements.
> 
> They are build-tested with allmodconfig on arm64, m68k, powerpc, riscv,
> s390, sparc64 and x86_64.
> 
> [...]

Applied to

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

Thanks!

[1/4] spi: Move comment about chipselect check to the right place
      commit: 6bfb15f34dd8c8a073e03a31c485ef5774b127df
[2/4] spi: Remove unused function spi_busnum_to_master()
      commit: bdc7ca008e1f5539e891187032cb2cbbc3decb5e
[3/4] spi: Reorder functions to simplify the next commit
      commit: fb51601bdf3a761ccd3f3d9dc6c03064f10f23aa
[4/4] spi: Make several public functions private to spi.c
      commit: da21fde0fdb393c2fbe0ae0735cc826cd55fd46f

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

      parent reply	other threads:[~2021-10-07 21:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07 12:14 [PATCH 0/4] spi: Various Cleanups Uwe Kleine-König
2021-10-07 12:14 ` [PATCH 1/4] spi: Move comment about chipselect check to the right place Uwe Kleine-König
2021-10-07 12:14 ` [PATCH 2/4] spi: Remove unused function spi_busnum_to_master() Uwe Kleine-König
2021-10-07 12:14 ` [PATCH 3/4] spi: Reorder functions to simplify the next commit Uwe Kleine-König
2021-10-07 12:14 ` [PATCH 4/4] spi: Make several public functions private to spi.c Uwe Kleine-König
2021-10-07 21:37 ` Mark Brown [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=163364264937.649954.11489762989707343828.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-spi@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.