From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Subject: Re: linux-next: manual merge of the omap_dss2 tree with the fbdev-current tree Date: Tue, 19 Apr 2011 10:03:30 +0300 Message-ID: <1303196610.2141.14.camel@deskari> References: <20110419132720.d86b8afd.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from na3sys009aog107.obsmtp.com ([74.125.149.197]:39557 "EHLO na3sys009aog107.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752217Ab1DSHDg (ORCPT ); Tue, 19 Apr 2011 03:03:36 -0400 In-Reply-To: <20110419132720.d86b8afd.sfr@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Archit Taneja , Paul Mundt Hi Stephen, On Tue, 2011-04-19 at 13:27 +1000, Stephen Rothwell wrote: > Hi Tomi, > > Today's linux-next merge of the omap_dss2 tree got a conflict in > drivers/video/omap2/dss/dss_features.c > drivers/video/omap2/dss/dss_features.h between commit 0b41136c0d2f > ("OMAP: DSS2: DSI: Fix DSI PLL power bug") from the fbdev-current tree > and commit 0f7d043bd56b ("OMAP4: DSS2: Register configuration changes for > DSI") from the omap_dss2 tree. > > I fixed it up (see below) and can carry the fix as necessary. This was actually my mistake, sorry. I had wrong commits in my for-next branch. I've update it to latest correct stuff, and the problem should disappear. Tomi