From: Mark Brown <broonie@kernel.org>
To: linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-spi@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v3 0/3] parport: Introduce module_parport_driver() and use it
Date: Thu, 04 Mar 2021 15:05:01 +0000 [thread overview]
Message-ID: <161487030158.30767.2653585264791466653.b4-ty@kernel.org> (raw)
In-Reply-To: <20210303091642.23929-1-andriy.shevchenko@linux.intel.com>
On Wed, 3 Mar 2021 11:16:39 +0200, Andy Shevchenko wrote:
> Introduce module_parport_driver() and use it.
> Greg or Mark, since we have this series tagged, can somebody of you pick it up?
>
> Changelog v3:
> - added tag on patch 1 (Sudip)
> - Cc'ed to Greg
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/3] parport: Introduce module_parport_driver() helper macro
commit: 9c9b536e1ee94558f1ae5ed8d13b76295b2dfef4
[2/3] spi: butterfly: Switch to use module_parport_driver()
commit: ef3a5316f41fa027cb00b158324a5ef7e3d1a277
[3/3] spi: lm70llp: Switch to use module_parport_driver()
commit: 7ea6fd9ba47853fb9e88b18d34fc60c71a3fd070
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:[~2021-03-04 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 9:16 Andy Shevchenko
2021-03-03 9:16 ` [PATCH v3 1/3] parport: Introduce module_parport_driver() helper macro Andy Shevchenko
2021-03-04 8:26 ` Greg Kroah-Hartman
2021-03-03 9:16 ` [PATCH v3 2/3] spi: butterfly: Switch to use module_parport_driver() Andy Shevchenko
2021-03-03 9:16 ` [PATCH v3 3/3] spi: lm70llp: " Andy Shevchenko
2021-03-03 20:24 ` [PATCH v3 0/3] parport: Introduce module_parport_driver() and use it Mark Brown
2021-03-04 8:27 ` Greg Kroah-Hartman
2021-03-04 15:05 ` 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=161487030158.30767.2653585264791466653.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=sudipm.mukherjee@gmail.com \
/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®