From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: jassi brar <jassisinghbrar@gmail.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCHES_v1] ASoC: Towards dropping runtime field from snd_soc_dai
Date: Tue, 23 Feb 2010 09:34:40 +0000 [thread overview]
Message-ID: <20100223093440.GA14629@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1b68c6791002222057t15ccff9ei395078c86cd4a67e@mail.gmail.com>
On Tue, Feb 23, 2010 at 01:57:30PM +0900, jassi brar wrote:
> I intended them to be 'git am' applied. Anyways, I hope I don't have to
> send attachments in future.
Yes, that was what I used to apply them - essentially what it does is to
stick the contents of the attachment onto the message subject and body
that it would normally use then process them so anything in the patch
that's replicated from the subject and body will end up at the end of
the body.
prev parent reply other threads:[~2010-02-23 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 6:55 [PATCHES_v1] ASoC: Towards dropping runtime field from snd_soc_dai jassi brar
2010-02-22 14:27 ` Mark Brown
2010-02-23 4:57 ` jassi brar
2010-02-23 9:34 ` 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=20100223093440.GA14629@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jassisinghbrar@gmail.com \
--cc=lrg@slimlogic.co.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).