mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Axel Lin <axel.lin@ingics.com>
Cc: Mark Brown <broonie@kernel.org>,
	Alistair Francis <alistair@alistair23.me>,
	Lars Ivar Miljeteig <lars.ivar.miljeteig@remarkable.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] regulator: sy7636a: Add terminating entry for platform_device_id table
Date: Wed, 16 Jun 2021 17:41:10 +0100	[thread overview]
Message-ID: <162386032647.25898.16073857531803041533.b4-ty@kernel.org> (raw)
In-Reply-To: <20210616034458.3499522-1-axel.lin@ingics.com>

On Wed, 16 Jun 2021 11:44:56 +0800, Axel Lin wrote:
> The platform_device_id table is supposed to be zero-terminated.

Applied to

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

Thanks!

[1/3] regulator: sy7636a: Add terminating entry for platform_device_id table
      commit: 686f6b31bf6cea71ca941b6dbf9e1388d54222b6
[2/3] regulator: sy7636a: Make regulator_desc static const
      commit: 31a89d297e196472875dc7d4a8f5dd0aaefcc0b4
[3/3] regulator: sy7636a: Use rdev_get_drvdata at proper place
      commit: 830c364f4a2299e8215c40f0a2ba9229c0fdeede

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

      parent reply	other threads:[~2021-06-16 16:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16  3:44 Axel Lin
2021-06-16  3:44 ` [PATCH 2/3] regulator: sy7636a: Make regulator_desc static const Axel Lin
2021-06-16  8:21   ` Alistair
2021-06-16  3:44 ` [PATCH 3/3] regulator: sy7636a: Use rdev_get_drvdata at proper place Axel Lin
2021-06-16  8:33   ` Alistair
2021-06-16  8:21 ` [PATCH 1/3] regulator: sy7636a: Add terminating entry for platform_device_id table Alistair
2021-06-16 16:41 ` 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=162386032647.25898.16073857531803041533.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alistair@alistair23.me \
    --cc=axel.lin@ingics.com \
    --cc=lars.ivar.miljeteig@remarkable.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®