All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: alsa-devel@alsa-project.org, Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 0/3] Fix breakages due to recent updates
Date: Sat, 26 Mar 2011 17:42:05 +0000	[thread overview]
Message-ID: <20110326174204.GH3535@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110326174040.GA20964@pengutronix.de>

On Sat, Mar 26, 2011 at 06:40:40PM +0100, Wolfram Sang wrote:

> Yes. Do you (or someone) happen to have a script ready which sends the
> cover-letter to the same people which get later added to the patches with
> --cc-cmd='script/maintainers.pl'?

My strong recommendation would be to never blindly use the output of
check_maintainers.pl directly in the first place but I'd exepect that
using the cover letter feature of git send-mail might do the trick.

      reply	other threads:[~2011-03-26 17:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25 15:51 [PATCH 0/3] Fix breakages due to recent updates Wolfram Sang
2011-03-25 15:51 ` [PATCH 1/3] ASoC: imx: set watermarks for mx2-dma Wolfram Sang
2011-03-25 15:51   ` Wolfram Sang
2011-03-26 11:42   ` Liam Girdwood
2011-03-26 11:42     ` Liam Girdwood
2011-03-25 15:51 ` [PATCH 2/3] ASoC: imx: fix burstsize for DMA Wolfram Sang
2011-03-25 15:51   ` Wolfram Sang
2011-03-26 11:42   ` Liam Girdwood
2011-03-26 11:42     ` Liam Girdwood
2011-03-25 15:51 ` [PATCH 3/3] ASoC: imx: remove superfluous code in imx-ssi.c Wolfram Sang
2011-03-25 15:51   ` Wolfram Sang
2011-03-26 11:42   ` Liam Girdwood
2011-03-26 11:42     ` Liam Girdwood
2011-03-26 17:35 ` [PATCH 0/3] Fix breakages due to recent updates Mark Brown
2011-03-26 17:40   ` Wolfram Sang
2011-03-26 17:42     ` Mark Brown [this message]

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=20110326174204.GH3535@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=s.hauer@pengutronix.de \
    --cc=w.sang@pengutronix.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.