From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Timur Tabi <timur@freescale.com>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
perex@perex.cz, tiwai@suse.de, lrg@ti.com,
linux-next@vger.kernel.org
Subject: Re: [PATCH] sound: fix trivial build error in mpc5200_dma.c
Date: Mon, 27 Feb 2012 23:56:31 +0000 [thread overview]
Message-ID: <20120227235630.GC23230@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F4BFC16.2090602@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 303 bytes --]
On Mon, Feb 27, 2012 at 03:56:38PM -0600, Timur Tabi wrote:
> Mark Brown wrote:
> > Please also try to use changelog headers consistent with the subsystem.
> Can you explain what that means? What are "changelog headers"?
The first line of the changelog which gets treated specially in various
ways.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-27 23:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 21:12 [PATCH] sound: fix trivial build error in mpc5200_dma.c Paul Gortmaker
2012-02-27 14:59 ` Mark Brown
2012-02-27 21:56 ` Timur Tabi
2012-02-27 23:56 ` Mark Brown [this message]
2012-02-28 0:43 ` Paul Gortmaker
2012-02-28 10:27 ` 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=20120227235630.GC23230@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-next@vger.kernel.org \
--cc=lrg@ti.com \
--cc=paul.gortmaker@windriver.com \
--cc=perex@perex.cz \
--cc=timur@freescale.com \
--cc=tiwai@suse.de \
/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.