From: Marek Vasut <marek.vasut@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, eric.y.miao@gmail.com,
linux-arm-kernel@lists.infradead.org,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 3/3] Zipit Z2 WM8750 aSoC driver
Date: Mon, 12 Apr 2010 14:34:45 +0200 [thread overview]
Message-ID: <201004121434.45793.marek.vasut@gmail.com> (raw)
In-Reply-To: <20100412103701.GA32087@rakim.wolfsonmicro.main>
Dne Po 12. dubna 2010 12:37:02 Mark Brown napsal(a):
> On Fri, Apr 09, 2010 at 11:48:22PM +0200, Marek Vasut wrote:
> > Mark, can you apply this as well? Thanks
>
> Applied, thanks.
>
> Stuff like this is one of the reasons it's better to send patches as new
> rather than as replies (and resend the whole series) - especially when
> you send many revisions of things it can be hard to track which versions
> are current.
Thanks a lot, will remember that. Thanks for guiding me through.
prev parent reply other threads:[~2010-04-12 12:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 4:00 [PATCH 1/3] WM8750: Convert to new API Marek Vasut
2010-04-05 4:00 ` [PATCH 2/3] WM8750: Fix SPITZ machine Marek Vasut
2010-04-05 4:00 ` [PATCH 3/3] Zipit Z2 WM8750 aSoC driver Marek Vasut
2010-04-05 4:10 ` [PATCH 1/3] WM8750: Convert to new API Marek Vasut
2010-04-05 4:13 ` Marek Vasut
2010-04-05 13:44 ` Mark Brown
2010-04-05 4:13 ` [PATCH 2/3] WM8750: Fix SPITZ machine Marek Vasut
2010-04-05 13:41 ` Mark Brown
2010-04-07 20:50 ` Marek Vasut
2010-04-08 9:40 ` Mark Brown
2010-04-08 14:51 ` [PATCH] WM8750: Convert to new API Marek Vasut
2010-04-08 14:58 ` Mark Brown
2010-04-05 4:13 ` [PATCH 3/3] Zipit Z2 WM8750 aSoC driver Marek Vasut
2010-04-05 13:42 ` Mark Brown
2010-04-05 14:12 ` Liam Girdwood
2010-04-09 21:48 ` Marek Vasut
2010-04-12 10:37 ` Mark Brown
2010-04-12 12:34 ` Marek Vasut [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=201004121434.45793.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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).