From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: regulator branch mess
Date: Tue, 4 Nov 2025 17:20:59 +0200 [thread overview]
Message-ID: <aQoZ22aT27wHBpbI@smile.fi.intel.com> (raw)
Hi, Mark.
Something bad happened to the regulator branch [1].
First of all, the merge message contains unneeded details (at least the
author's email signature). Second, the few lines series becomes 3kLoCs
merge commit. I think the base was wrong and `b4` (if you use that one)
took too much to merge.
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/ci.git/commit/?h=regulator-6.19
--
With Best Regards,
Andy Shevchenko
next reply other threads:[~2025-11-04 15:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 15:20 Andy Shevchenko [this message]
2025-11-04 15:32 ` regulator branch mess 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
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=aQoZ22aT27wHBpbI@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=broonie@kernel.org \
--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