From: jassi brar <jassisinghbrar@gmail.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com,
ben-linux@fluff.org, Jassi Brar <jassi.brar@samsung.com>
Subject: Re: Reforming S3C I2S towards supporting I2Sv4
Date: Wed, 10 Mar 2010 18:02:26 +0900 [thread overview]
Message-ID: <1b68c6791003100102k1697b053y1cd7a9d492f76e6a@mail.gmail.com> (raw)
In-Reply-To: <1268211069.3760.10.camel@odin>
On Wed, Mar 10, 2010 at 5:51 PM, Liam Girdwood <lrg@slimlogic.co.uk> wrote:
> On Wed, 2010-03-10 at 17:35 +0900, jassi brar wrote:
>> Folks please ignore the second copy of patches 11-20.
>> Git send-email seems to have 'buffer' ... first <git send-email
>> *.patch> command emailed only patches 1-10 second copy was actually
>> sent
>> when I tried to resend 11-20 again thinking they have been dropped.
>> Sorry.
>
> Ah, I did wonder when Acking the first set...
My another mistake(not CCing you) saved you 30 more emails though :)
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2010-03-10 9:02 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 [this message]
2010-03-10 10:20 ` Mark Brown
2010-03-10 14:23 ` Mark Brown
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=1b68c6791003100102k1697b053y1cd7a9d492f76e6a@mail.gmail.com \
--to=jassisinghbrar@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jassi.brar@samsung.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).