linux-kernel - Re: [PATCH v3 00/20] Intel platform driver code movement

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] [day] [month] [year] [list]

Message-ID: <b521dd02-4ea6-c604-b851-ee41e8d1ad33@redhat.com>
Date:   Thu, 19 Aug 2021 16:08:44 +0200
From:   Hans de Goede <hdegoede@...hat.com>
To:     Andy Shevchenko <andy.shevchenko@...il.com>
Cc:     Kate Hsuan <hpa@...hat.com>, Alex Hung <alex.hung@...onical.com>,
        Mark Gross <mgross@...ux.intel.com>,
        Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
        AceLan Kao <acelan.kao@...onical.com>,
        Jithu Joseph <jithu.joseph@...el.com>,
        Maurice Ma <maurice.ma@...el.com>,
        Sujith Thomas <sujith.thomas@...el.com>,
        Rajneesh Bhardwaj <irenic.rajneesh@...il.com>,
        Zha Qipeng <qipeng.zha@...el.com>,
        Mika Westerberg <mika.westerberg@...ux.intel.com>,
        "David E . Box" <david.e.box@...ux.intel.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Dell.Client.Kernel@...l.com,
        Platform Driver <platform-driver-x86@...r.kernel.org>
Subject: Re: [PATCH v3 00/20] Intel platform driver code movement

Hi,

On 8/19/21 4:01 PM, Andy Shevchenko wrote:
> On Thu, Aug 19, 2021 at 4:34 PM Hans de Goede <hdegoede@...hat.com> wrote:
>> On 8/19/21 3:31 PM, Hans de Goede wrote:
> 
> ...
> 
>> Note that drivers/platform/x86/intel_ips.h is deliberately not moved
>> (for now) since it is also used by the i915 driver.
>>
>> My plan is to merge a follow-up patch moving that through drm-intel-next
>> once 5.15-rc1 is out.
> 
> Why we can't do it in the same patch?

Because the intel-drm code is seeing a lot of churn, so that will
cause conflicts. It will be a lot easier to do the move of that
last file through the drm-intel-next tree once this rename series
has landed in 5.15-rc1

Regards,

Hans