From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 03B721D545 for ; Mon, 26 Feb 2024 11:20:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.7 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708946422; cv=none; b=c3PoFAw/6T62bV287ctjrSrhxAEfDCGhiF2qxjC3adERxUl6P0KXntF3H9GXUYmPb3FIa4YZ2cf3jEd+zZqd8RoUgLUIDQgwiqXQYc4SICPb0QBEq+tnxbVAPBhITOQjMevuLsLULS462EEshkuKfu2KRPS90KXolGHMvvD75uA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708946422; c=relaxed/simple; bh=ebfQqnPQVSD0OLSlfPoVFPLfxXa7rGkBnVgKvxWgKNQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=cyRljQNsP5HEtmXmaJ6GIV1ROvuS1OPJBiHgOSm4n1uSSI4ajJs+KylVJl1BR5BVVAh+hGOQP/adndncRjzCvFj6f/7eOFHHoBMBwBFzJrOsGOzjhELjinaFu6YfP0WYQ47emaxdjX7M7BE6gtvSjHos9MOpsBqmYfbXH0yWQdc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=fZ8Koq38; arc=none smtp.client-ip=192.198.163.7 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="fZ8Koq38" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1708946420; x=1740482420; h=from:to:cc:subject:in-reply-to:references:date: message-id:mime-version; bh=ebfQqnPQVSD0OLSlfPoVFPLfxXa7rGkBnVgKvxWgKNQ=; b=fZ8Koq38Z7Pc7hpo3zWpcpXQ37ue4ImTrT+VVecqWW3cqMsboXbZps/t 0VaaDeU0YJMLt/YVokx7KWU3lBrRGKUfsCtF1X+Sw3rHdNxxvi2byiPPZ Ei3UDvsvyA9LeqS5PjI6ePuC9OgUcvMl51uUybS80dixlze8P40UQI22i YW1TgSgyCzx55mblScDeVToiTPB2Q+PhuFYQgYsfghBzmWflmVILXo2Tx davhoS9n65p61211kngD4+4nbndbntFnuPz5Qof1S1jhRWJ9d6Le0YwsL K3ljV+c4M6oUL4SmSkiUDr1iIis1b9iGnfW6VQMXkdQiJ9j4SPiA4/B9F Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10995"; a="28649287" X-IronPort-AV: E=Sophos;i="6.06,185,1705392000"; d="scan'208";a="28649287" Received: from orviesa001.jf.intel.com ([10.64.159.141]) by fmvoesa101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Feb 2024 03:20:19 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.06,185,1705392000"; d="scan'208";a="44117309" Received: from hibeid-mobl.amr.corp.intel.com (HELO localhost) ([10.252.46.254]) by smtpauth.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Feb 2024 03:20:12 -0800 From: Jani Nikula To: Lucas De Marchi , Stephen Rothwell Cc: Arnd Bergmann , Arnd Bergmann , Oded Gabbay , Thomas =?utf-8?Q?Hellstr=C3=B6m?= , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Dave Airlie , Daniel Vetter , Rodrigo Vivi , Matt Roper , Matthew Brost , Riana Tauro , Daniele Ceraolo Spurio , 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 In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20240213134817.3347574-1-arnd@kernel.org> <877cj88lck.fsf@intel.com> <17209419-093b-4674-8b43-06c92312ef61@app.fastmail.com> <20240221172117.243799cf@canb.auug.org.au> Date: Mon, 26 Feb 2024 13:20:10 +0200 Message-ID: <87h6hvo4k5.fsf@intel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Wed, 21 Feb 2024, Lucas De Marchi 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