[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87h6hvo4k5.fsf@intel.com>
Date: Mon, 26 Feb 2024 13:20:10 +0200
From: Jani Nikula <jani.nikula@...ux.intel.com>
To: Lucas De Marchi <lucas.demarchi@...el.com>, Stephen Rothwell
<sfr@...b.auug.org.au>
Cc: Arnd Bergmann <arnd@...db.de>, Arnd Bergmann <arnd@...nel.org>, Oded
Gabbay <ogabbay@...nel.org>, Thomas
Hellström <thomas.hellstrom@...ux.intel.com>, Maarten
Lankhorst <maarten.lankhorst@...ux.intel.com>, Maxime Ripard
<mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>, Dave Airlie
<airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>, Rodrigo Vivi
<rodrigo.vivi@...el.com>, Matt Roper <matthew.d.roper@...el.com>, Matthew
Brost <matthew.brost@...el.com>, Riana Tauro <riana.tauro@...el.com>,
Daniele Ceraolo Spurio <daniele.ceraolospurio@...el.com>,
intel-xe@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org
Subject: Re: Re: [PATCH] drm/xe: skip building debugfs code for
CONFIG_DEBUG_FS=n
On Wed, 21 Feb 2024, Lucas De Marchi <lucas.demarchi@...el.com> wrote:
> Looking at drm-intel and drm-misc, they are using a special
> for-linux-next. We may eventually adopt the same workflow, but I will
> have to check with other maintainers.
The idea is to try to better reflect what's actually going to next. For
example, drm-intel-next starts targeting "next next" after about
-rc6. But we haven't properly automated the cutoff point, it only kicks
in at release. So there's still a window when linux-next sees "next
next" stuff that gets dropped. Using drm-xe-next directly makes for a
longer window.
BR,
Jani.
--
Jani Nikula, Intel
Powered by blists - more mailing lists