From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Pull request question for Mark (ASoC)
Date: Thu, 20 Sep 2012 07:43:08 -0400 [thread overview]
Message-ID: <20120920114307.GI17666@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120920073218.GA10230@gmail.com>
On Thu, Sep 20, 2012 at 09:32:18AM +0200, Lee Jones wrote:
> I have a pull request for you, but at least one of the patches
> touches the MOP500 driver as well as ux500 platform code. If I
> split them up into for-asoc-next and for-arm-soc-next branches
> there I it will cause conflicts in arch/arm/mach-ux500/*.
> Is it okay to send the 6 patches I have for ASoC, all of which
> are encapsulated in sound/soc/ux500/ through the arm-soc tree
> with the rest of my patches please?
I have no problem with that but please post whatever code you're
thinking of sending as well as the pull requests, don't just post the
pull requests.
next prev parent reply other threads:[~2012-09-20 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 7:32 Pull request question for Mark (ASoC) Lee Jones
2012-09-20 11:43 ` Mark Brown [this message]
[not found] ` <CABVG=qc6-DVzMhogCopaS+rdHm5ZRM2q_1L_k9xXGWRrxzrfBw@mail.gmail.com>
2012-09-20 11:56 ` Lee Jones
2012-09-20 11:59 ` Mark Brown
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=20120920114307.GI17666@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).