linux-kernel - Re: linux-next: manual merge of the drm tree with Linus' tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 24 Aug 2012 17:12:34 +1000
From:	Dave Airlie <airlied@...il.com>
To:	Jani Nikula <jani.nikula@...el.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Dave Airlie <airlied@...ux.ie>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Daniel Vetter <daniel.vetter@...ll.ch>
Subject: Re: linux-next: manual merge of the drm tree with Linus' tree

On Fri, Aug 24, 2012 at 5:13 PM, Jani Nikula <jani.nikula@...el.com> wrote:
> On Fri, 24 Aug 2012, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>> Hi Dave,
>>
>> Today's linux-next merge of the drm tree got a conflict in
>> drivers/gpu/drm/i915/intel_modes.c between commit 4eab81366465
>> ("drm/i915: extract connector update from intel_ddc_get_modes() for
>> reuse") from Linus' tree and commit 451023dc32d4 ("drm: remove the
>> raw_edid field from struct drm_display_info") from the drm tree.
>
> Ugh, both from me, sorry about that. Wasn't sure when or in what order
> they'd go in.
>
>> I fixed it up (see below) and can carry the fix as necessary.
>
> I'm not quite sure what the patch below is against, but just removing
> the reference to raw_edid from a slightly different place is the way to
> go. Like you seem to do, so:
>
> Acked-by: Jani Nikula <jani.nikula@...el.com>
>
> I can also provide a patch against drm-next if needed.

That applied fine, I pulled it in for tomorrow -next.

Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/