From: Mark Brown <broonie@kernel.org>
To: Vinod Koul <vinod.koul@intel.com>
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] Revert "ASoC: Intel: Skylake: fix memory leak"
Date: Tue, 5 Jan 2016 12:11:41 +0000 [thread overview]
Message-ID: <20160105121141.GZ16023@sirena.org.uk> (raw)
In-Reply-To: <20160105115417.GL2940@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 555 bytes --]
On Tue, Jan 05, 2016 at 05:24:17PM +0530, Vinod Koul wrote:
> On Tue, Jan 05, 2016 at 11:46:22AM +0000, Mark Brown wrote:
> > Please use subject lines matching the style for the subsystem.
> Is this an automated mail :) but its signed!
No, I type those out by hand.
> Btw am not sure why this is not proper, isn't revert followed by old patch
> title the right style for revert patches..? what did i miss...
Patches are patches are patches, reverts are patches like any other and
should still have subject lines matching the style for the subsystem.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2016-01-05 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 11:46 [PATCH 1/2] Revert "ASoC: Intel: Skylake: fix memory leak" Vinod Koul
2016-01-05 11:46 ` [PATCH 2/2] ASoC: Intel: Skylake: Fix the memory leak Vinod Koul
2016-01-05 12:33 ` Applied "ASoC: Intel: Skylake: Fix the memory leak" to the asoc tree Mark Brown
2016-01-05 11:46 ` [PATCH 1/2] Revert "ASoC: Intel: Skylake: fix memory leak" Mark Brown
2016-01-05 11:54 ` Vinod Koul
2016-01-05 12:11 ` Mark Brown [this message]
2016-01-05 13:18 ` Vinod Koul
2016-01-05 12:33 ` Applied "ASoC: Intel: Skylake: Revert previous broken fix memory leak fix" to the asoc 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=20160105121141.GZ16023@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.com \
--cc=vinod.koul@intel.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