From: Mark Brown <broonie@kernel.org>
To: Ashish Kumar <ashish.kumar@nxp.com>,
linux-spi@vger.kernel.org, Yogesh Gaur <yogeshgaur.83@gmail.com>,
kuldip dwivedi <kuldip.dwivedi@puresoftware.com>,
linux-kernel@vger.kernel.org
Cc: Arokia Samy <arokia.samy@nxp.com>,
Ard Biesheuvel <Ard.Biesheuvel@arm.com>,
Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>,
Varun Sethi <V.Sethi@nxp.com>, Paul Yang <Paul.Yang@arm.com>
Subject: Re: [PATCH v3] spi: spi-nxp-fspi: Add ACPI support
Date: Thu, 17 Sep 2020 19:58:23 +0100 [thread overview]
Message-ID: <160036909795.20353.12392603785811661559.b4-ty@kernel.org> (raw)
In-Reply-To: <20200911130331.6313-1-kuldip.dwivedi@puresoftware.com>
On Fri, 11 Sep 2020 18:33:31 +0530, kuldip dwivedi wrote:
> Currently NXP fspi driver has support of DT only. Adding ACPI
> support to the driver so that it can be used by UEFI firmware
> booting in ACPI mode. This driver will be probed if any firmware
> will expose HID "NXP0009" in DSDT table.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: spi-nxp-fspi: Add ACPI support
commit: 55ab8487e01d18466ddf596acc7a11e8c53b2812
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:[~2020-09-17 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 13:03 kuldip dwivedi
2020-09-11 13:25 ` [EXT] " Ashish Kumar
2020-09-17 18:58 ` 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=160036909795.20353.12392603785811661559.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=Ard.Biesheuvel@arm.com \
--cc=Paul.Yang@arm.com \
--cc=Samer.El-Haj-Mahmoud@arm.com \
--cc=V.Sethi@nxp.com \
--cc=arokia.samy@nxp.com \
--cc=ashish.kumar@nxp.com \
--cc=kuldip.dwivedi@puresoftware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=yogeshgaur.83@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®