From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Likely Date: Sun, 28 Feb 2010 07:04:03 +0000 Subject: Re: [PATCH 0/3] Rework MPC5121 DIU support (for 2.6.34) Message-Id: List-Id: References: <1267307902-31939-1-git-send-email-agust@denx.de> In-Reply-To: <1267307902-31939-1-git-send-email-agust@denx.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Anatolij Gustschin Cc: linux-fbdev@vger.kernel.org, wd@denx.de, dzu@denx.de, jrigby@gmail.com, linuxppc-dev@ozlabs.org, yorksun@freescale.com Hi Anatolij, On Sat, Feb 27, 2010 at 2:58 PM, Anatolij Gustschin wrote: > This patch series rework DIU support patch submitted > previously with the patch series for updating MPC5121 > support in mainline. It doesn't add new panel timing data > to the framebuffer driver anymore. Instead we now allow > encoding this data in the device tree. First two patches > add this support. Thanks for this work. I've made specific comments on the individual patches. There are some details to be worked out, but I think it is moving in the right direction. > It is intended for inclusion in 2.6.34, since without > DIU support patch framebuffer doesn't work on mpc5121. It's actually late for 2.6.34. Unless it is a bug fix, I stop picking up new patches somewhere in the -rc7 or -rc8 timerframe, and I am definitely in bug-fix-only mode once the merge window has opened. I do this to ensure all patches receive a decent amount of linux-next exposure before I ask Linus to pull them. I'll being picking up new patches for 2.6.35 into my -next branch after 2.6.34-rc1 is released. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd.