From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: regulator branch mess
Date: Wed, 5 Nov 2025 07:24:50 +0200 [thread overview]
Message-ID: <aQrfolXgeWs8A_gK@smile.fi.intel.com> (raw)
In-Reply-To: <20251104221551.GA2968640@mit.edu>
On Tue, Nov 04, 2025 at 05:15:51PM -0500, Theodore Ts'o wrote:
> Andy, I don't know what github is doing to confuse you, but my
I haven't told anything about Git Hub, I talked about web representation on
kernel.org.
> preferred way of understanding what is in a merge commit is to use the
> command line tools, which are less likely to lie (or at least, to be
> confusing):
Yep, less confusing. The problem of the confusion here is the merge commit
text, that only describes the merge of the small series but also implies bump
from v6.18-rc3 to v6.18-rc4. Other subsystems I follow usually do an explicit
back-merges to the rcX whenever is needed. But as I told Mark, I'm fine if
that was a deliberate (known) move. Now it's all clear.
Thanks for helping me to understand this!
> % git log --pretty=oneline regulator/for-next ^base/master
> 9de2057bbdfb58f4d9bb1476135317cd3fe6aa52 (regulator/for-next, regulator/for-6.19, regulator/HEAD) regulator: pf9453: optimize PMIC PF9453 driver
> 2ecc8c089802e033d2e5204d21a9f467e2517df9 regulator: pf9453: remove unused I2C_LT register
> 0144a2b29d95af8523c308116de65d398d6e935b regulator: pf9453: remove low power mode
> a2d4691b3fec6a2360e4ec953d06819ea055c3e7 regulator: pf9453: change the device ID register address
> 252abf2d07d33b1c70a59ba1c9395ba42bbd793e regulator: Small cleanup in of_get_regulation_constraints()
> 28039efa4d8e8bbf98b066133a906bd4e307d496 MAINTAINERS: remove obsolete file entry in DIALOG SEMICONDUCTOR DRIVERS
> dc74a00c7661a14a672ea7660caca5c4aa661a79 regulator: pca9450: add input supply links
> 4c33cef58965eb655a0ac8e243aa323581ec025f regulator: pca9450: link regulator inputs to supply groups
> 86df0030b71d7172317d957df17524a7fd6232d4 regulator: dt-bindings: nxp,pca9450: document input supplies
> 01313661b248c5ba586acae09bff57077dbec0a5 regulator: Let raspberrypi drivers depend on ARM
> d054cc3a2ccfb19484f3b54d69b6e416832dc8f4 regulator: rpmh-regulator: Add RPMH regulator support for PMR735D
> f76dbe127f1b5910e37dfe307d2de5c13d61ed89 regulator: dt-bindings: qcom,rpmh: Add support for PMR735D
> 5263cd81578f99a00b2dd7de1da2b570b96a1b7c rpmh-regulators: Update rpmh-regulator driver and
> fb25114cd760c13cf177d9ac37837fafcc9657b5 regulator: sy7636a: add gpios and input regulator
> 65efe5404d151767653c7b7dd39bd2e7ad532c2d regulator: rpmh-regulator: Add RPMH regulator support for Glymur
> 6a8cdef7dc2a4c0dbde3f7d7100b3d99712a766b regulator: rpmh-regulator: Add support for new resource name format
> 1356c98ef911e14ccfaf374800840ce5bdcb3bbd regulator: dt-bindings: rpmh-regulator: Update pmic-id DT prop info for new CMD-DB
> 835dfb12fc389f36eb007657f163bd1c539dcd45 regulator: dt-bindings: rpmh-regulator : Add compatibles for PMH01XX & PMCX0102
> 433e294c3c5b5d2020085a0e36c1cb47b694690a regulator: core: forward undervoltage events downstream by default
> 6277a486a7faaa6c87f4bf1d59a2de233a093248 regulator: dt-bindings: Convert Dialog DA9211 Regulators to DT schema
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-11-05 5:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 15:20 regulator branch mess Andy Shevchenko
2025-11-04 15:32 ` Mark Brown
2025-11-04 15:48 ` Andy Shevchenko
2025-11-04 15:51 ` Andy Shevchenko
2025-11-04 16:01 ` Mark Brown
2025-11-04 16:11 ` Andy Shevchenko
2025-11-04 16:18 ` Andy Shevchenko
2025-11-04 16:30 ` Mark Brown
2025-11-04 16:54 ` Andy Shevchenko
2025-11-04 17:05 ` Mark Brown
2025-11-04 17:11 ` Andy Shevchenko
2025-11-04 22:15 ` Theodore Ts'o
2025-11-05 5:24 ` Andy Shevchenko [this message]
2025-11-05 15:08 ` Theodore Ts'o
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=aQrfolXgeWs8A_gK@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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