From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Arnd Bergmann" <arnd@kernel.org>,
"Oded Gabbay" <ogabbay@kernel.org>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Dave Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Matt Roper" <matthew.d.roper@intel.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Riana Tauro" <riana.tauro@intel.com>,
"Daniele Ceraolo Spurio" <daniele.ceraolospurio@intel.com>,
intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH] drm/xe: skip building debugfs code for CONFIG_DEBUG_FS=n
Date: Mon, 26 Feb 2024 13:20:10 +0200 [thread overview]
Message-ID: <87h6hvo4k5.fsf@intel.com> (raw)
In-Reply-To: <zospejkdqekbndbov3ubbbvr5skxwohezeslzciivhxakfjoek@oa5sp2ffcfix>
On Wed, 21 Feb 2024, Lucas De Marchi <lucas.demarchi@intel.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
prev parent reply other threads:[~2024-02-26 11:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 13:48 [PATCH] drm/xe: skip building debugfs code for CONFIG_DEBUG_FS=n Arnd Bergmann
2024-02-13 13:51 ` ✗ CI.Patch_applied: failure for " Patchwork
2024-02-13 14:55 ` [PATCH] " Jani Nikula
2024-02-13 14:58 ` Arnd Bergmann
2024-02-21 5:29 ` Lucas De Marchi
2024-02-21 6:21 ` Stephen Rothwell
2024-02-21 19:45 ` Lucas De Marchi
2024-02-21 21:59 ` Stephen Rothwell
2024-02-26 11:20 ` Jani Nikula [this message]
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=87h6hvo4k5.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=daniel@ffwll.ch \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tzimmermann@suse.de \
/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.