linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: linux-omap mailing list <linux-omap@vger.kernel.org>,
	lfbdev-ml <linux-fbdev@vger.kernel.org>
Subject: Re: [GIT PULL] OMAP DSS for v3.2
Date: Mon, 17 Oct 2011 06:49:55 +0000	[thread overview]
Message-ID: <4E9BD013.3050903@ti.com> (raw)
In-Reply-To: <4E9B52E7.7020601@gmx.de>

On 10/17/2011 12:55 AM, Florian Tobias Schandinat wrote:
> Hi Tomi,
>
> On 10/07/2011 07:20 AM, Tomi Valkeinen wrote:
>> Hi Florian,
>>
>> Please pull OMAP DSS patches for v3.2 merge window.
>
> Pulled.

Thanks.

>> Note that there are some conflicts with other trees. The board file
>> conflicts are trivial, changes in code which just happen to be next to
>> each other. The LCD driver conflicts are even simpler, there were
>> changes to them from some other tree, but I have removed the files.
>>
>> The conflicts have been solved properly by Stephen in linux-next:
>>
>> https://github.com/sfrothwell/linux-next/commit/3e31b3042760e3906d0a275d7adedfaf55ee5b0a
>>
>> I also attached the output from git show, as github seems to show the
>> full diff for the merge commit.
>>
>> Are you ok with the conflicts?
>
> No problem.
> Well, as I understand, Linus prefers to see (and solve) these conflicts himself,
> so I don't have any work with them at all. I'd only have to resolve them if
> Linus gave up and that would probably point to a more fundamental issue in the
> workflow, like changes going mainline via the wrong tree or such things.

This is also my understanding. However, Linus isn't that fond of ARM 
board files, which is where the conflicts are...

One could argue that the board file changes should go through the OMAP 
tree, but both the driver and the board files need to be changed at the 
same time to keep kernel compiling.

  Tomi

      reply	other threads:[~2011-10-17  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07  7:20 [GIT PULL] OMAP DSS for v3.2 Tomi Valkeinen
2011-10-16 21:55 ` Florian Tobias Schandinat
2011-10-17  6:49   ` Tomi Valkeinen [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=4E9BD013.3050903@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=FlorianSchandinat@gmx.de \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-omap@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).