From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: ola.o.lilja@stericsson.com, linus.walleij@linaro.org,
alsa-devel@alsa-project.org, arnd@arndb.de
Subject: Re: [GIT PULL] MOP500 Audio patches due for ASoC
Date: Thu, 20 Sep 2012 07:57:15 -0400 [thread overview]
Message-ID: <20120920115713.GK17666@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120920113715.GB17429@gmail.com>
On Thu, Sep 20, 2012 at 01:37:15PM +0200, Lee Jones wrote:
> The following changes since commit 5698bd757d55b1bb87edd1a9744ab09c142abfc2:
>
> Linux 3.6-rc6 (2012-09-16 14:58:51 -0700)
>
> are available in the git repository at:
>
> git://git.linaro.org/people/ljones/linux-3.0-ux500.git for-asoc-next
>
> for you to fetch changes up to b4cad7af6665743647f28119b689e1552326d4da:
>
> Documentation: Define the MSP Driver Device Tree bindings (2012-09-20 09:10:59 +0200)
Please post the actual patches for review as well. The normal thing is
to post the patches as a followup to the pull request making the pull
request a cover letter for the series, and obviously if they are from
your previous serieses it's been some considerable time since that
happend.
next prev parent reply other threads:[~2012-09-20 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 11:37 [GIT PULL] MOP500 Audio patches due for ASoC Lee Jones
2012-09-20 11:57 ` Mark Brown [this message]
2012-09-20 12:02 ` Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2012-09-20 12:09 Lee Jones
2012-09-20 12:56 ` Mark Brown
2012-09-20 13:06 ` Lee Jones
2012-09-27 15:01 ` Lee Jones
2012-09-28 12:37 ` Mark Brown
2012-09-28 14:59 ` Lee Jones
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=20120920115713.GK17666@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=ola.o.lilja@stericsson.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 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).