From: Mark Brown <broonie@kernel.org>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
linux-kernel@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH] Revert "regulator: core: Add support for active-discharge configuration"
Date: Fri, 25 Mar 2016 18:19:29 +0000 [thread overview]
Message-ID: <20160325181929.GD5028@sirena.org.uk> (raw)
In-Reply-To: <56F5700D.2000105@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
On Fri, Mar 25, 2016 at 07:06:21PM +0200, Vladimir Zapolskiy wrote:
> On 25.03.2016 17:45, Mark Brown wrote:
> > Nope, they're patches like other patches. A big part of what the
> > subject line does is help people work out what they need to look at,
> > something that doesn't pattern match doesn't fulfil that need.
> regarding pattern matching just remove ^ from the regexp and people
> be aware of this "regulator: core" change.
The pattern matching in this case is typically being done by human
beings.
> Please look at 1 hour old 1701f680407c ("Revert "ppdev: use new parport
> device model" ") --- that's IMHO the proper way to create and apply
> reverts.
The fact that a change happens to have been generated with a revert has
no technical impact, you're not communicating with machines here but
rather with people. Yes, some people don't mind especially if they're
just directly publishing the commit (where it matters much less) but
that doesn't override all other considerations.
> And I disagree with the modified subject and commit message done by you
> and without a notice mentioning this your change in the commit message.
I already published it so it's a bit late now.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-25 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 19:52 [PATCH] Revert "regulator: core: Add support for active-discharge configuration" Vladimir Zapolskiy
2016-03-25 11:10 ` Mark Brown
2016-03-25 12:31 ` Vladimir Zapolskiy
2016-03-25 14:58 ` Mark Brown
2016-03-25 14:52 ` Vladimir Zapolskiy
2016-03-25 15:45 ` Mark Brown
2016-03-25 17:06 ` Vladimir Zapolskiy
2016-03-25 18:19 ` Mark Brown [this message]
2016-03-25 16:43 ` Applied "regulator: core: Remove duplicate copy of active-discharge parsing" to the regulator tree Mark Brown
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=20160325181929.GD5028@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=vladimir_zapolskiy@mentor.com \
/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