public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH] Revert "regulator: core: Add support for active-discharge configuration"
Date: Fri, 25 Mar 2016 14:58:47 +0000	[thread overview]
Message-ID: <20160325145847.GE2566@sirena.org.uk> (raw)
In-Reply-To: <56F52FB3.6050008@mentor.com>

[-- Attachment #1: Type: text/plain, Size: 520 bytes --]

On Fri, Mar 25, 2016 at 02:31:47PM +0200, Vladimir Zapolskiy wrote:

> I agree, but the subsystem name is found in the name of the reverted commit.

That doesn't help if it's not at the start of the subject line of the
e-mail.

> Do you ask me to resumbit the change changing the subject to
> 'regulator: core: Revert "regulator: core: Add support for active-discharg
>  configuration"'?

Well, I applied it already so no but in future yes, reverts are patches
like any other and should follow exactly the same process.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-03-25 14:58 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 [this message]
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
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=20160325145847.GE2566@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=ldewangan@nvidia.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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