linux-kernel - Re: Re: [PATCH] drm/xe: skip building debugfs code for CONFIG_DEBUG

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]

Message-ID: <zospejkdqekbndbov3ubbbvr5skxwohezeslzciivhxakfjoek@oa5sp2ffcfix>
Date: Wed, 21 Feb 2024 13:45:35 -0600
From: Lucas De Marchi <lucas.demarchi@...el.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Arnd Bergmann <arnd@...db.de>, Jani Nikula <jani.nikula@...ux.intel.com>,
	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, Feb 21, 2024 at 05:21:17PM +1100, Stephen Rothwell wrote:
>Hi Lucas,
>
>On Tue, 20 Feb 2024 23:29:54 -0600 Lucas De Marchi <lucas.demarchi@...el.com> wrote:
>>
>> Looking at https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=2d5c7b7eb345249cb34d42cbc2b97b4c57ea944e
>> it seems we still don't have drm-xe-next branch in linux-next.
>>
>> Stephen, could you please add it? Or do I have to do something on my end
>> before that?  This is the branch:
>>
>> https://gitlab.freedesktop.org/drm/xe/kernel drm-xe-next
>
>Added from tomorrow.  Currently the only contact is yourself.  Do you
>want anyone else (or a mailing list) as well?
>
>Do you want the drm-xe-fixes branch included as well?

I don't think it's needed since drm-xe-next covers what is in
drm-xe-fixes. Please add other maintainers and mailing list:

M:      Oded Gabbay <ogabbay@...nel.org>
M:      Thomas Hellström <thomas.hellstrom@...ux.intel.com>
L:      intel-xe@...ts.freedesktop.org

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.

thanks
Lucas De Marchi

>
>Thanks for adding your subsystem tree as a participant of linux-next.  As
>you may know, this is not a judgement of your code.  The purpose of
>linux-next is for integration testing and to lower the impact of
>conflicts between subsystems in the next merge window.
>
>You will need to ensure that the patches/commits in your tree/series have
>been:
>     * submitted under GPL v2 (or later) and include the Contributor's
>        Signed-off-by,
>     * posted to the relevant mailing list,
>     * reviewed by you (or another maintainer of your subsystem tree),
>     * successfully unit tested, and
>     * destined for the current or next Linux merge window.
>
>Basically, this should be just what you would send to Linus (or ask him
>to fetch).  It is allowed to be rebased if you deem it necessary.
>
>-- 
>Cheers,
>Stephen Rothwell
>sfr@...b.auug.org.au