From: Mark Brown <broonie@kernel.org>
To: linus.walleij@linaro.org, brgl@bgdev.pl,
William Breathitt Gray <william.gray@linaro.org>
Cc: andriy.shevchenko@linux.intel.com, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v2 0/6] Migrate IDIO-16 GPIO drivers to regmap API
Date: Mon, 06 Mar 2023 14:09:13 +0000 [thread overview]
Message-ID: <167811175334.98202.15503041463855908266.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1677515341.git.william.gray@linaro.org>
On Mon, 27 Feb 2023 11:45:21 -0500, William Breathitt Gray wrote:
> Changes in v2:
> - Utilize memset32() to set status_buf for no_status case
> - Utilize GENMASK() to generate status_buf mask
> - Move no_status kernel doc line under runtime_pm line
> - Add comma to end of idio_16_names initialization list
> - Set io_port to true in idio_16_regmap_config
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next
Thanks!
[1/6] regmap-irq: Add no_status support
commit: 4d60cac951fd2dfbf261b83abb805748abc8b995
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
next prev parent reply other threads:[~2023-03-06 14:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 16:45 William Breathitt Gray
2023-02-27 16:45 ` [PATCH v2 1/6] regmap-irq: Add no_status support William Breathitt Gray
2023-03-06 10:11 ` Bartosz Golaszewski
2023-03-10 12:01 ` William Breathitt Gray
2023-03-15 13:28 ` Mark Brown
2023-02-27 16:45 ` [PATCH v2 2/6] gpio: 104-dio-48e: Utilize no_status regmap-irq flag William Breathitt Gray
2023-02-27 16:45 ` [PATCH v2 3/6] gpio: idio-16: Migrate to the regmap API William Breathitt Gray
2023-02-27 16:45 ` [PATCH v2 4/6] gpio: 104-idio-16: " William Breathitt Gray
2023-02-27 16:45 ` [PATCH v2 5/6] gpio: pci-idio-16: " William Breathitt Gray
2023-03-22 16:37 ` Bartosz Golaszewski
2023-02-27 16:45 ` [PATCH v2 6/6] gpio: idio-16: Remove unused legacy interface William Breathitt Gray
2023-03-06 14:09 ` Mark Brown [this message]
2023-03-06 14:12 ` [PATCH v2 0/6] Migrate IDIO-16 GPIO drivers to regmap API Linus Walleij
2023-03-15 10:02 ` Bartosz Golaszewski
2023-03-15 10:14 ` Linus Walleij
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=167811175334.98202.15503041463855908266.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=william.gray@linaro.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®