From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL RESEND] rk3288 i2s controller
Date: Fri, 26 Sep 2014 00:40:23 +0200 [thread overview]
Message-ID: <201409260040.23894.arnd@arndb.de> (raw)
In-Reply-To: <4038555.EtoLsBADBk@phil>
On Monday 22 September 2014, Heiko St?bner wrote:
> While everything will of course work in next/dt of arm-soc where both my
> past pulls landed, it would produce build errors in rockchip/dts1 [if the
> kbuild
> robot tried to "make dtbs" there] as the dma patches not in there.
The right approach for this case would be to send a pull request with this
commit based on the earlier one that has the dependency, or to send it
as a plain patch.
I've cherry-picked the one commit from this branch on top of next/dt, so
everything should be good now.
Arnd
prev parent reply other threads:[~2014-09-25 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 14:26 [GIT PULL RESEND] rk3288 i2s controller Heiko Stübner
2014-09-25 22:40 ` Arnd Bergmann [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=201409260040.23894.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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