2021-01-28 12:05:52

by Axel Lin

Subject: [PATCH] regulator: pf8x00: Fix typo for PF8200 chip name

Trivial typo fix.

Signed-off-by: Axel Lin <[email protected]>
---
drivers/regulator/pf8x00-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/regulator/pf8x00-regulator.c b/drivers/regulator/pf8x00-regulator.c
index 827da25466cc..9b28bd63208d 100644
--- a/drivers/regulator/pf8x00-regulator.c
+++ b/drivers/regulator/pf8x00-regulator.c
@@ -529,7 +529,7 @@ static int pf8x00_identify(struct pf8x00_chip *chip)
name = "PF8121A";
break;
case PF8200:
- name = "PF8100";
+ name = "PF8200";
break;
default:
dev_err(chip->dev, "Unknown pf8x00 device id 0x%x\n", dev_id);
--
2.25.1

2021-01-28 14:35:13

by Adrien Grassein

Subject: Re: [PATCH] regulator: pf8x00: Fix typo for PF8200 chip name

Le jeu. 28 janv. 2021 à 13:02, Axel Lin <[email protected]> a écrit :
>
> Trivial typo fix.
>
> Signed-off-by: Axel Lin <[email protected]>
> ---
> drivers/regulator/pf8x00-regulator.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/regulator/pf8x00-regulator.c b/drivers/regulator/pf8x00-regulator.c
> index 827da25466cc..9b28bd63208d 100644
> --- a/drivers/regulator/pf8x00-regulator.c
> +++ b/drivers/regulator/pf8x00-regulator.c
> @@ -529,7 +529,7 @@ static int pf8x00_identify(struct pf8x00_chip *chip)
> name = "PF8121A";
> break;
> case PF8200:
> - name = "PF8100";
> + name = "PF8200";
> break;
> default:
> dev_err(chip->dev, "Unknown pf8x00 device id 0x%x\n", dev_id);
> --
> 2.25.1
>

Reviewed-by: Adrien Grassein <[email protected]>

2021-01-28 21:00:14

by Mark Brown

Subject: Re: [PATCH] regulator: pf8x00: Fix typo for PF8200 chip name

On Thu, 28 Jan 2021 20:01:51 +0800, Axel Lin wrote:
> Trivial typo fix.

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: pf8x00: Fix typo for PF8200 chip name
commit: 64f09ea1b551189f491ffb626fdccc2c31fe2d70

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