From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: (subset) [PATCH v1 0/3] spi: CS code, variables and comments clarification
Date: Wed, 06 Mar 2024 21:59:50 +0000 [thread overview]
Message-ID: <170976239071.258774.10326274744681538196.b4-ty@kernel.org> (raw)
In-Reply-To: <20240306160114.3471398-1-andriy.shevchenko@linux.intel.com>
On Wed, 06 Mar 2024 17:59:39 +0200, Andy Shevchenko wrote:
> There are a few duplicated code pieces, inconsitent types and comments
> regarding to Chip Select pins. Refactor and clarify that.
>
> Andy Shevchenko (3):
> spi: Exctract spi_set_all_cs_unused() helper
> spi: Exctract spi_dev_check_cs() helper
> spi: Fix multiple issues with Chip Select variables and comments
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/3] spi: Exctract spi_set_all_cs_unused() helper
commit: 5ee91605ad9ad363766a7ed13dc7d47f5102982a
[2/3] spi: Exctract spi_dev_check_cs() helper
commit: 9086d0f23b7c292f162a828967975e29e97c0680
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
prev parent reply other threads:[~2024-03-06 21:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 15:59 Andy Shevchenko
2024-03-06 15:59 ` [PATCH v1 1/3] spi: Exctract spi_set_all_cs_unused() helper Andy Shevchenko
2024-03-06 15:59 ` [PATCH v1 2/3] spi: Exctract spi_dev_check_cs() helper Andy Shevchenko
2024-03-06 15:59 ` [PATCH v1 3/3] spi: Fix multiple issues with Chip Select variables and comments Andy Shevchenko
2024-03-06 18:08 ` Mark Brown
2024-03-06 20:12 ` Andy Shevchenko
2024-03-07 15:08 ` Andy Shevchenko
2024-03-06 21:59 ` 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=170976239071.258774.10326274744681538196.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.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
all inboxes | Powered by JetHome®