[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5ad5de1d-1cd3-b1cd-2880-c8df78e4db58@intel.com>
Date: Fri, 12 Nov 2021 12:18:18 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Lucas De Marchi <lucas.demarchi@...el.com>,
Peter Zijlstra <peterz@...radead.org>
Cc: intel-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
x86@...nel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
xen-devel@...ts.xenproject.org,
Daniel Vetter <daniel.vetter@...ll.ch>
Subject: Re: [PATCH 0/2] Nuke PAGE_KERNEL_IO
On 11/12/21 12:09 PM, Lucas De Marchi wrote:
> The intention was to merge this through the tip tree. Although now I'm
> not sure. Options:
>
> 1) take the first patch through the drm-intel tree and apply the
> second patch later
> 2) take everything through the drm tree
> 3) take everything through the tip tree
>
> What's your preference here?
It's fine with me to take it through tip unless that causes a problem
for anyone. I was planning on doing queuing it after -rc1.
Powered by blists - more mailing lists