From: Mark Brown <broonie@kernel.org>
To: Adrien Grassein <adrien.grassein@gmail.com>
Cc: robh+dt@kernel.org, linux-kernel@vger.kernel.org,
jagan@amarulasolutions.com, devicetree@vger.kernel.org,
lgirdwood@gmail.com
Subject: Re: [PATCH v5 0/6] Fix issues on pf8x00 driver
Date: Fri, 15 Jan 2021 18:19:51 +0000 [thread overview]
Message-ID: <161073479107.12431.4350059208898304988.b4-ty@kernel.org> (raw)
In-Reply-To: <20210114174714.122561-1-adrien.grassein@gmail.com>
On Thu, 14 Jan 2021 18:47:08 +0100, Adrien Grassein wrote:
> this patch set aims is to fix some issues contains in the pf8x00 driver.
> Some issues are documentation ones, some others are in code.
>
> These issues where found while developing another version of the same
> driver. I prefer to share with you the patch for it.
>
> I do these patches on the master branch of the linux-next repository.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/6] regulator: pf8x00: add a doc for the module
commit: 4d23b84d1fcd1eadbc5c6cd93e76b02a8d191d66
[2/6] regulator: dt-bindings: pf8x00: fix nxp,phase-shift doc
commit: 988d0d42509a2c1fad0844a6e8f9c7bce7c930dd
[3/6] regulator: dt-bindings: pf8x00: mark nxp,ilim-ma property as deprecated
commit: 34b860aa0b6221b21eea6bac76357063f525b561
[4/6] regulator: pf8x00: mark nxp,ilim-ma property as deprecated
commit: 245f5f65229a6c6f5b04fa90221b44818a928916
[5/6] regulator: pf8x00: use linear range for buck 1-6
commit: 35a93349932e0e04c284f8a4954f3d1236c97d85
[6/6] regulator: pf8x00: fix nxp,phase-shift
commit: 475a5d85ff62f7ca73f51f23977e7e3ec8c9f906
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
prev parent reply other threads:[~2021-01-15 18:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 17:47 Adrien Grassein
2021-01-14 17:47 ` [PATCH v5 1/6] regulator: pf8x00: add a doc for the module Adrien Grassein
2021-01-14 17:47 ` [PATCH v5 2/6] regulator: dt-bindings: pf8x00: fix nxp,phase-shift doc Adrien Grassein
2021-01-14 17:47 ` [PATCH v5 3/6] regulator: dt-bindings: pf8x00: mark nxp,ilim-ma property as deprecated Adrien Grassein
2021-01-14 17:47 ` [PATCH v5 4/6] regulator: " Adrien Grassein
2021-01-14 17:47 ` [PATCH v5 5/6] regulator: pf8x00: use linear range for buck 1-6 Adrien Grassein
2021-01-14 17:47 ` [PATCH v5 6/6] regulator: pf8x00: fix nxp,phase-shift Adrien Grassein
2021-01-15 18:19 ` 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=161073479107.12431.4350059208898304988.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=adrien.grassein@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jagan@amarulasolutions.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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®