From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] staging: imx-drm-core: skip components whose parent device is disabled
Date: Wed, 23 Apr 2014 15:44:53 +0800 [thread overview]
Message-ID: <20140423074451.GE2523@dragon> (raw)
In-Reply-To: <20140422215506.GC24070@n2100.arm.linux.org.uk>
On Tue, Apr 22, 2014 at 10:55:06PM +0100, Russell King - ARM Linux wrote:
> So care to explain why there were _zero_ merge conflicts from -rc time
> before the merge window up to about a week _into_ the merge window, and
> then suddenly arm-soc starts conflicting not only locally here but _also_
> in linux-next.
>
> That stinks of arm-soc merging new stuff *during* the merge window.
I'm not sure that's the case.
It seems to me that the merge conflict was reported by Stephen Rothwell
one month ahead of the merge window [1].
Shawn
[1] https://lkml.org/lkml/2014/2/25/21
>
> And don't try to deny that - remember, I run a build system here locally,
> and I _manually_ merge Linus' tip into my tip (which contains *everything*
> including the staged changes for imx-drm and those binding changes) _and_
> finally arm-soc's for-next branch, and there were _zero_ conflicts at the
> start of the merge window.
next prev parent reply other threads:[~2014-04-23 7:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 2:02 [PATCH v2] staging: imx-drm-core: skip components whose parent device is disabled Shawn Guo
2014-04-14 8:01 ` Philipp Zabel
2014-04-18 20:42 ` Russell King - ARM Linux
2014-04-19 5:53 ` Shawn Guo
2014-04-19 8:42 ` Russell King - ARM Linux
2014-04-19 11:00 ` Shawn Guo
2014-04-21 14:22 ` Olof Johansson
2014-04-21 23:31 ` Shawn Guo
2014-04-22 20:49 ` Arnd Bergmann
2014-04-22 21:55 ` Russell King - ARM Linux
2014-04-23 7:44 ` Shawn Guo [this message]
2014-04-23 9:00 ` Russell King - ARM Linux
2014-04-24 21:36 ` Arnd Bergmann
2014-04-26 10:20 ` Russell King - ARM Linux
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=20140423074451.GE2523@dragon \
--to=shawn.guo@freescale.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.