From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jassi Brar <jassi.brar@samsung.com>
Cc: alsa-devel@alsa-project.org, ben-linux@fluff.org
Subject: Re: Reforming S3C I2S towards supporting I2Sv4
Date: Wed, 10 Mar 2010 14:23:15 +0000 [thread overview]
Message-ID: <20100310142314.GD6850@sirena.org.uk> (raw)
In-Reply-To: <1268207335-9947-1-git-send-email-jassi.brar@samsung.com>
On Wed, Mar 10, 2010 at 04:48:55PM +0900, Jassi Brar wrote:
> I have prepared some patches that debug and modify the behaviour of
> extant S3C I2S support towards managing I2Sv4 controllers as well.
OK, I think that's everything. I've not applied anything after the
header move yet due to the need for an ack from Ben. Any patches I
didn't specifically comment on are OK. Overall it's all good, most of
the issues are minor.
In future could you please use --no-chain-reply-to when sending patches
to avoid massively deep threads in threaded mail readers (the git
default is changing in 1.7.0 for this very reason). It's also best to
send the cover letter first and tell git send-email that everything
should be sent in reply to that - this way people are likely to see the
cover letter before the patches.
next prev parent reply other threads:[~2010-03-10 14:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 7:48 Reforming S3C I2S towards supporting I2Sv4 Jassi Brar
2010-03-10 8:24 ` Liam Girdwood
2010-03-10 8:31 ` jassi brar
2010-03-10 9:04 ` Liam Girdwood
2010-03-10 9:22 ` jassi brar
2010-03-10 10:18 ` Mark Brown
2010-03-10 8:35 ` jassi brar
2010-03-10 8:51 ` Liam Girdwood
2010-03-10 9:02 ` jassi brar
2010-03-10 10:20 ` Mark Brown
2010-03-10 14:23 ` Mark Brown [this message]
2010-04-06 0:33 ` jassi brar
2010-04-27 2:10 ` jassi brar
2010-04-27 2:58 ` Ben Dooks
2010-04-27 4:25 ` jassi brar
2010-05-02 4:38 ` Kyungmin Park
2010-05-02 8:28 ` jassi brar
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=20100310142314.GD6850@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=jassi.brar@samsung.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 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.