All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Guodong Xu <guodong.xu@linaro.org>
Cc: Mark Brown <broonie@kernel.org>,
	lee.jones@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com,
	xuwei5@hisilicon.com, catalin.marinas@arm.com,
	will.deacon@arm.com, lgirdwood@gmail.com, broonie@kernel.org,
	khilman@baylibre.com, arnd@arndb.de,
	gregory.clement@free-electrons.com, horms+renesas@verge.net.au,
	olof@lixom.net, thomas.petazzoni@free-electrons.com,
	yamada.masahiro@socionext.com, riku.voipio@linaro.org,
	treding@nvidia.com, krzk@kernel.org, eric@anholt.net,
	damm+renesas@opensource.se, ard.biesheuvel@linaro.org,
	linus.walleij@linaro.org, geert+renesas@glider.be,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	hw.wangxiaoyin@hisilicon.com,
	Jeremy Linton <lintonrjeremy@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Applied "regulator: hi6421: Describe consumed platform device" to the regulator tree
Date: Wed, 07 Jun 2017 20:32:09 +0100	[thread overview]
Message-ID: <E1dIggb-0003ma-2K@debutante> (raw)
In-Reply-To: <20170602085117.27474-5-guodong.xu@linaro.org>

The patch

   regulator: hi6421: Describe consumed platform device

has been applied to the regulator tree at

   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.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 a8ea49d7f589fac1994a3b0af59f25cb284f3eb6 Mon Sep 17 00:00:00 2001
From: Guodong Xu <guodong.xu@linaro.org>
Date: Wed, 7 Jun 2017 15:06:04 +0800
Subject: [PATCH] regulator: hi6421: Describe consumed platform device

The hi6421-regulator driver consumes a similarly named platform device.
Adding that to the module device table, allows modprobe to locate this
driver once the device is created.

Signed-off-by: Guodong Xu <guodong.xu@linaro.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
 drivers/regulator/hi6421-regulator.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/drivers/regulator/hi6421-regulator.c b/drivers/regulator/hi6421-regulator.c
index 62c5f5445d44..259c3a865ac6 100644
--- a/drivers/regulator/hi6421-regulator.c
+++ b/drivers/regulator/hi6421-regulator.c
@@ -621,7 +621,14 @@ static int hi6421_regulator_probe(struct platform_device *pdev)
 	return 0;
 }
 
+static const struct platform_device_id hi6421_regulator_table[] = {
+	{ .name = "hi6421-regulator" },
+	{},
+};
+MODULE_DEVICE_TABLE(platform, hi6421_regulator_table);
+
 static struct platform_driver hi6421_regulator_driver = {
+	.id_table = hi6421_regulator_table,
 	.driver = {
 		.name	= "hi6421-regulator",
 	},
-- 
2.11.0

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Guodong Xu <guodong.xu@linaro.org>
Cc: Mark Brown <broonie@kernel.org>,
	lee.jones@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com,
	xuwei5@hisilicon.com, catalin.marinas@arm.com,
	will.deacon@arm.com, lgirdwood@gmail.combroonie@kernel.org,
	khilman@baylibre.com, arnd@arndb.de,
	gregory.clement@free-electrons.com, horms+renesas@verge.net.au,
	olof@lixom.net, thomas.petazzoni@free-electrons.com,
	yamada.masahiro@socionext.com, riku.voipio@linaro.org,
	treding@nvidia.com, krzk@kernel.org, eric@anholt.net,
	damm+renesas@opensource.se, ard.biesheuvel@linaro.org,
	linus.walleij@linaro.org, geert+renesas@glider.be,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	hw.wangxiaoyin@hisilicon.com,
	Jeremy Linton
	<lintonrjeremy@gmail.com>linux-kernel@vger.kernel.org
Subject: Applied "regulator: hi6421: Describe consumed platform device" to the regulator tree
Date: Wed, 07 Jun 2017 20:32:09 +0100	[thread overview]
Message-ID: <E1dIggb-0003ma-2K@debutante> (raw)
In-Reply-To: <20170602085117.27474-5-guodong.xu@linaro.org>

The patch

   regulator: hi6421: Describe consumed platform device

has been applied to the regulator tree at

   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.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 a8ea49d7f589fac1994a3b0af59f25cb284f3eb6 Mon Sep 17 00:00:00 2001
From: Guodong Xu <guodong.xu@linaro.org>
Date: Wed, 7 Jun 2017 15:06:04 +0800
Subject: [PATCH] regulator: hi6421: Describe consumed platform device

The hi6421-regulator driver consumes a similarly named platform device.
Adding that to the module device table, allows modprobe to locate this
driver once the device is created.

Signed-off-by: Guodong Xu <guodong.xu@linaro.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
 drivers/regulator/hi6421-regulator.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/drivers/regulator/hi6421-regulator.c b/drivers/regulator/hi6421-regulator.c
index 62c5f5445d44..259c3a865ac6 100644
--- a/drivers/regulator/hi6421-regulator.c
+++ b/drivers/regulator/hi6421-regulator.c
@@ -621,7 +621,14 @@ static int hi6421_regulator_probe(struct platform_device *pdev)
 	return 0;
 }
 
+static const struct platform_device_id hi6421_regulator_table[] = {
+	{ .name = "hi6421-regulator" },
+	{},
+};
+MODULE_DEVICE_TABLE(platform, hi6421_regulator_table);
+
 static struct platform_driver hi6421_regulator_driver = {
+	.id_table = hi6421_regulator_table,
 	.driver = {
 		.name	= "hi6421-regulator",
 	},
-- 
2.11.0

WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Applied "regulator: hi6421: Describe consumed platform device" to the regulator tree
Date: Wed, 07 Jun 2017 20:32:09 +0100	[thread overview]
Message-ID: <E1dIggb-0003ma-2K@debutante> (raw)
In-Reply-To: <20170602085117.27474-5-guodong.xu@linaro.org>

The patch

   regulator: hi6421: Describe consumed platform device

has been applied to the regulator tree at

   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.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 a8ea49d7f589fac1994a3b0af59f25cb284f3eb6 Mon Sep 17 00:00:00 2001
From: Guodong Xu <guodong.xu@linaro.org>
Date: Wed, 7 Jun 2017 15:06:04 +0800
Subject: [PATCH] regulator: hi6421: Describe consumed platform device

The hi6421-regulator driver consumes a similarly named platform device.
Adding that to the module device table, allows modprobe to locate this
driver once the device is created.

Signed-off-by: Guodong Xu <guodong.xu@linaro.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
 drivers/regulator/hi6421-regulator.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/drivers/regulator/hi6421-regulator.c b/drivers/regulator/hi6421-regulator.c
index 62c5f5445d44..259c3a865ac6 100644
--- a/drivers/regulator/hi6421-regulator.c
+++ b/drivers/regulator/hi6421-regulator.c
@@ -621,7 +621,14 @@ static int hi6421_regulator_probe(struct platform_device *pdev)
 	return 0;
 }
 
+static const struct platform_device_id hi6421_regulator_table[] = {
+	{ .name = "hi6421-regulator" },
+	{},
+};
+MODULE_DEVICE_TABLE(platform, hi6421_regulator_table);
+
 static struct platform_driver hi6421_regulator_driver = {
+	.id_table = hi6421_regulator_table,
 	.driver = {
 		.name	= "hi6421-regulator",
 	},
-- 
2.11.0

  reply	other threads:[~2017-06-07 19:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02  8:51 [PATCH v2 0/6] MFD: add driver for HiSilicon Hi6421v530 PMIC Guodong Xu
2017-06-02  8:51 ` Guodong Xu
2017-06-02  8:51 ` Guodong Xu
2017-06-02  8:51 ` [PATCH v2 1/6] dt-bindings: mfd: hi6421: Add hi6421v530 compatible string Guodong Xu
2017-06-02  8:51   ` Guodong Xu
2017-06-02  8:51 ` [PATCH v2 2/6] mfd: hi6421-pmic: add support for HiSilicon Hi6421v530 Guodong Xu
2017-06-02  8:51   ` Guodong Xu
2017-06-02  8:51   ` Guodong Xu
2017-06-02  8:51 ` [PATCH v2 3/6] regulator: hi6421v530: add driver for hi6421v530 voltage regulator Guodong Xu
2017-06-02  8:51   ` Guodong Xu
2017-06-02  8:51 ` [PATCH v2 4/6] regulator: hi6421: Describe consumed platform device Guodong Xu
2017-06-02  8:51   ` Guodong Xu
2017-06-07 19:32   ` Mark Brown [this message]
2017-06-07 19:32     ` Applied "regulator: hi6421: Describe consumed platform device" to the regulator tree Mark Brown
2017-06-07 19:32     ` Mark Brown
2017-06-02  8:51 ` [PATCH v2 5/6] arm64: dts: hikey960: add device node for pmic and regulators Guodong Xu
2017-06-02  8:51   ` Guodong Xu
2017-06-02  8:51   ` Guodong Xu
2017-06-02  8:51 ` [PATCH v2 6/6] arm64: defconfig: enable support hi6421v530 PMIC Guodong Xu
2017-06-02  8:51   ` Guodong Xu

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=E1dIggb-0003ma-2K@debutante \
    --to=broonie@kernel.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=damm+renesas@opensource.se \
    --cc=devicetree@vger.kernel.org \
    --cc=eric@anholt.net \
    --cc=geert+renesas@glider.be \
    --cc=gregory.clement@free-electrons.com \
    --cc=guodong.xu@linaro.org \
    --cc=horms+renesas@verge.net.au \
    --cc=hw.wangxiaoyin@hisilicon.com \
    --cc=khilman@baylibre.com \
    --cc=krzk@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=lintonrjeremy@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=olof@lixom.net \
    --cc=riku.voipio@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=treding@nvidia.com \
    --cc=will.deacon@arm.com \
    --cc=xuwei5@hisilicon.com \
    --cc=yamada.masahiro@socionext.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.