[0/2] Fix spelling of "regulator"
mbox series

Message ID 20201124183730.2250690-1-michael@fossekall.de
Headers show
Series
  • Fix spelling of "regulator"
Related show

Message

Michael Klein Nov. 24, 2020, 6:37 p.m. UTC
Michael Klein (2):
  Documentation: mcp16502-regulator: fix spelling mistake
  mfd: fix spelling mistakes

 .../devicetree/bindings/regulator/mcp16502-regulator.txt      | 2 +-
 drivers/regulator/da9055-regulator.c                          | 4 ++--
 include/linux/mfd/da9055/reg.h                                | 4 ++--
 include/linux/mfd/si476x-core.h                               | 2 +-
 4 files changed, 6 insertions(+), 6 deletions(-)

Comments

Mark Brown Nov. 25, 2020, noon UTC | #1
On Tue, 24 Nov 2020 19:37:28 +0100, Michael Klein wrote:
> Michael Klein (2):
>   Documentation: mcp16502-regulator: fix spelling mistake
>   mfd: fix spelling mistakes
> 
>  .../devicetree/bindings/regulator/mcp16502-regulator.txt      | 2 +-
>  drivers/regulator/da9055-regulator.c                          | 4 ++--
>  include/linux/mfd/da9055/reg.h                                | 4 ++--
>  include/linux/mfd/si476x-core.h                               | 2 +-
>  4 files changed, 6 insertions(+), 6 deletions(-)

Applied to

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

Thanks!

[1/1] regulator: mcp16502-regulator: fix spelling mistake
      commit: 33f369efbce15e034db4faabeec8502d7d236859

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