From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Applied "spi: meson: Add GXBB compatible" to the spi tree
Date: Mon, 12 Sep 2016 20:12:28 +0100 [thread overview]
Message-ID: <E1bjWea-0003hH-1K@debutante> (raw)
In-Reply-To: <1473261223-15412-5-git-send-email-jbrunet@baylibre.com>
The patch
spi: meson: Add GXBB compatible
has been applied to the spi tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
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
>From 2f58ea64bd8931bd7709732fe0a96e0bfb44a00b Mon Sep 17 00:00:00 2001
From: Neil Armstrong <narmstrong@baylibre.com>
Date: Thu, 8 Sep 2016 09:53:26 +0200
Subject: [PATCH] spi: meson: Add GXBB compatible
Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Acked-by: Kevin Hilman <khilman@baylibre.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
drivers/spi/spi-meson-spifc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/spi/spi-meson-spifc.c b/drivers/spi/spi-meson-spifc.c
index 2465259f6241..616566e793c6 100644
--- a/drivers/spi/spi-meson-spifc.c
+++ b/drivers/spi/spi-meson-spifc.c
@@ -442,6 +442,7 @@ static const struct dev_pm_ops meson_spifc_pm_ops = {
static const struct of_device_id meson_spifc_dt_match[] = {
{ .compatible = "amlogic,meson6-spifc", },
+ { .compatible = "amlogic,meson-gxbb-spifc", },
{ },
};
MODULE_DEVICE_TABLE(of, meson_spifc_dt_match);
--
2.8.1
next prev parent reply other threads:[~2016-09-12 19:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 15:13 [PATCH 0/7] ARM: amlogic: Add spifc support to Amlogic's GXBB family Jerome Brunet
2016-09-07 15:13 ` [PATCH 1/7] pinctrl: amlogic: gxbb: add spifc pins Jerome Brunet
2016-09-08 18:08 ` Kevin Hilman
2016-09-07 15:13 ` [PATCH 2/7] pinctrl: amlogic: gxbb: add nand pins Jerome Brunet
2016-09-08 18:09 ` Kevin Hilman
2016-09-07 15:13 ` [PATCH 3/7] clk: gxbb: expose spifc clock Jerome Brunet
2016-09-07 21:27 ` Stephen Boyd
2016-09-08 18:12 ` Kevin Hilman
2016-09-07 15:13 ` [PATCH 4/7] spi: meson: Add GXBB compatible Jerome Brunet
2016-09-07 18:58 ` Mark Brown
2016-09-08 7:44 ` Neil Armstrong
2016-09-12 19:12 ` Mark Brown [this message]
2016-09-07 15:13 ` [PATCH 5/7] dt-bindings: spi-meson: Add GXBB Compatible string Jerome Brunet
2016-09-12 19:12 ` Applied "spi: meson: Add GXBB Compatible string" to the spi tree Mark Brown
2016-09-07 15:13 ` [PATCH 6/7] ARM64: dts: amlogic: add pins for spifc Jerome Brunet
2016-09-07 15:13 ` [PATCH 7/7] ARM64: dts: meson-gxbb: Add SPIFC node Jerome Brunet
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=E1bjWea-0003hH-1K@debutante \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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