From: Jyri Sarha <jsarha-l0cyMroinI0@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Cc: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
tomi.valkeinen-l0cyMroinI0@public.gmane.org
Subject: Re: [PATCH 0/3] ARM: dts: am335x-* Add blue-and-red-wiring propery to lcdc nodes
Date: Mon, 19 Sep 2016 10:30:41 +0300 [thread overview]
Message-ID: <f8124caf-9752-c970-fd41-404ea4d983a9@ti.com> (raw)
In-Reply-To: <20160916150242.vbvpuokftychkdfz-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
On 09/16/16 18:02, Tony Lindgren wrote:
> * Jyri Sarha <jsarha-l0cyMroinI0@public.gmane.org> [160916 04:50]:
>> > These patches complete the am335x LCDC color errata fix[1]. The
>> > functional patches are now queued for v4.9.
>> >
>> > The patch for am335x-boneblack.dts is delayed until v4.10 or v4.9-rc
>> > phase to avoid conflickt with BBB HDMI audio DTS patch that slipped
>> > into tda998x pull request.
>> >
>> > [1] http://www.spinics.net/lists/devicetree/msg141246.html
> OK. Are these safe to merge even if the dts changes get merged before
> the driver changes? Or does it break something if merged out of order?
Yes, they are safe. The new property just simply is not interpreted and
everything works as before.
BR,
Jyri
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-09-19 7:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 11:50 [PATCH 0/3] ARM: dts: am335x-* Add blue-and-red-wiring propery to lcdc nodes Jyri Sarha
[not found] ` <cover.1474025756.git.jsarha-l0cyMroinI0@public.gmane.org>
2016-09-16 11:50 ` [PATCH 1/3] ARM: dts: am335x-evm: Add blue-and-red-wiring -property to lcdc node Jyri Sarha
[not found] ` <34893e286d16c281098063d2a4fec985acbf8818.1474025756.git.jsarha-l0cyMroinI0@public.gmane.org>
2016-09-16 22:17 ` Nishanth Menon
[not found] ` <a0e00898-80fb-8242-aafb-6e4d3f650345-l0cyMroinI0@public.gmane.org>
2016-09-19 7:55 ` Jyri Sarha
[not found] ` <3052854a-de30-0e6d-3084-6788733c7118-l0cyMroinI0@public.gmane.org>
2016-09-19 14:47 ` Nishanth Menon
2016-09-16 11:50 ` [PATCH 2/3] ARM: dts: am335x-evmsk: Whitespace cleanup of lcdc related nodes Jyri Sarha
2016-09-16 11:50 ` [PATCH 3/3] ARM: dts: am335x-evmsk: Add blue-and-red-wiring -property to lcdc node Jyri Sarha
2016-09-16 15:02 ` [PATCH 0/3] ARM: dts: am335x-* Add blue-and-red-wiring propery to lcdc nodes Tony Lindgren
[not found] ` <20160916150242.vbvpuokftychkdfz-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2016-09-19 7:30 ` Jyri Sarha [this message]
[not found] ` <f8124caf-9752-c970-fd41-404ea4d983a9-l0cyMroinI0@public.gmane.org>
2016-09-19 23:14 ` Tony Lindgren
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=f8124caf-9752-c970-fd41-404ea4d983a9@ti.com \
--to=jsarha-l0cymroini0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tomi.valkeinen-l0cyMroinI0@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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