All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: Mark Brown <broonie@kernel.org>
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 19:06:21 +0200	[thread overview]
Message-ID: <56F5700D.2000105@mentor.com> (raw)
In-Reply-To: <20160325154507.GG2566@sirena.org.uk>

Mark,

On 25.03.2016 17:45, Mark Brown wrote:
> On Fri, Mar 25, 2016 at 04:52:32PM +0200, Vladimir Zapolskiy wrote:
>> On 25.03.2016 13:10, Mark Brown wrote:
> 
>>> Please submit patches using subject lines reflecting the style for the
>>> subsystem.  This makes it easier for people to identify relevant
>>> patches.
> 
>> Okay, submitting of reverted patches is different I believe:
> 
>> http://www.spinics.net/lists/arm-kernel/msg75667.html
> 
> 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.

I understand that the reverted commit is a maintainer's fault and by
renaming the subject you may hide it, so talking about people needs
please let them know that the change _reverts_ another commit.

I can not add Fixes: tag, because the change does not fix a commit, and
there is no Reverts: tag due to its obvious redundancy.

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.

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.

--
With best wishes,
Vladimir

  reply	other threads:[~2016-03-25 17:06 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 [this message]
2016-03-25 18:19         ` Mark Brown
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=56F5700D.2000105@mentor.com \
    --to=vladimir_zapolskiy@mentor.com \
    --cc=broonie@kernel.org \
    --cc=ldewangan@nvidia.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.