From: Mark Brown <broonie@kernel.org>
To: Kukjin Kim <kgene@kernel.org>
Cc: 'Olof Johansson' <olof@lixom.net>,
'Arnd Bergmann' <arnd@arndb.de>,
Padmavathi Venna <padma.v@samsung.com>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: Broken device trees for exynos in linux-next
Date: Fri, 16 Aug 2013 01:42:02 +0100 [thread overview]
Message-ID: <20130816004202.GA28985@sirena.org.uk> (raw)
In-Reply-To: <20130816003557.GJ30073@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
On Fri, Aug 16, 2013 at 01:35:57AM +0100, Mark Brown wrote:
> On Fri, Aug 16, 2013 at 09:04:28AM +0900, Kukjin Kim wrote:
> > NO, the build breakage is due to commit 6187288f15bc ("ARM: dts: exynos5250:
> > move common i2s properties to exynos5 dtsi" which is in Mark Brown's tree.
> > Mark, pleaser revert it in your tree...
> I'll do that but I don't know if that's then going to break anything
> else. This sort of bisection/cross tree issue does come up a lot with
> the Samsung SoCs - it'd be good if you could remind the people working
> on them about the need to make sure that when there are dependencies
> they're handled when things are merged.
I also had to revert "ARM: dts: Change i2s compatible string on
exynos5250" from my tree since it depended on the above commit. I
suspect this may leave the driver broken and we'll need a new version
before the merge window...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-16 0:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 16:43 Broken device trees for exynos in linux-next Olof Johansson
2013-08-16 0:04 ` Kukjin Kim
2013-08-16 0:35 ` Mark Brown
2013-08-16 0:42 ` Mark Brown [this message]
2013-08-16 3:34 ` Padma Venkat
2013-08-16 16:04 ` Olof Johansson
2013-08-16 18:03 ` Mark Brown
2013-08-17 10:40 ` Kukjin Kim
2013-08-19 15:15 ` Kevin Hilman
2013-08-22 9:55 ` Kukjin Kim
2013-08-22 16:20 ` Olof Johansson
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=20130816004202.GA28985@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=padma.v@samsung.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