From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============4579317957938806328==" MIME-Version: 1.0 From: Borislav Petkov To: kbuild-all@lists.01.org Subject: Re: [patch 06/12] x86/entry: Convert system vectors to irq stack macro Date: Tue, 09 Feb 2021 11:46:19 +0100 Message-ID: <20210209104619.GA15191@zn.tnic> In-Reply-To: <536a6b24-fadb-cb2a-8259-dadd3730c6ce@intel.com> List-Id: --===============4579317957938806328== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Tue, Feb 09, 2021 at 04:57:09PM +0800, Rong Chen wrote: > Thanks for the help, how can we identify the patches for tip tree, > could you please guide us? I guess something like: cat patch | ./scripts/get_maintainer.pl -m --no-r --no-l For a tip patch, it should give, among others: x86(a)kernel.org (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)) which is the tip ML. You'd need to play with this a bit to see what works best. Also, I'm wondering if it would make sense to have some special syntax to let the 0day bot know on which tree to apply the patches after scraping or to even be able to say: "do not test" when sending just an example patch which is not supposed to be used anyway and thus you don't have to waste infra cycles on it. HTH. -- = Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette --===============4579317957938806328==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 764B8C433DB for ; Tue, 9 Feb 2021 10:53:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1F62360232 for ; Tue, 9 Feb 2021 10:53:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232174AbhBIKwv (ORCPT ); Tue, 9 Feb 2021 05:52:51 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49976 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231672AbhBIKrF (ORCPT ); Tue, 9 Feb 2021 05:47:05 -0500 Received: from mail.skyhub.de (mail.skyhub.de [IPv6:2a01:4f8:190:11c2::b:1457]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 44374C061786 for ; Tue, 9 Feb 2021 02:46:25 -0800 (PST) Received: from zn.tnic (p200300ec2f2f38005896b2f9ed512c58.dip0.t-ipconnect.de [IPv6:2003:ec:2f2f:3800:5896:b2f9:ed51:2c58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 25E321EC056A; Tue, 9 Feb 2021 11:46:23 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1612867583; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=Unei56clXZHQ5Xap4ehdEmREbfheuAoq1P8ROyril1Y=; b=InCdq2yN+u20bpeaCJVeFYY6a633LzD+su3otU9ZIOvh/xa3MGrKlM7pnFnZq61Ag7XSPV ZKvXji5ai0pp1NyriR0nRQPUCbwkl67WEfl3I2rE6+0Jl7RjZmXbMqhIEPzzJVfNibxMCA 2dNOFKmWt1knJdLrMzJFRpoL2Hv8ivU= Date: Tue, 9 Feb 2021 11:46:19 +0100 From: Borislav Petkov To: Rong Chen Cc: Peter Zijlstra , kernel test robot , Thomas Gleixner , LKML , kbuild-all@lists.01.org, x86@kernel.org, Kees Cook Subject: Re: [kbuild-all] Re: [patch 06/12] x86/entry: Convert system vectors to irq stack macro Message-ID: <20210209104619.GA15191@zn.tnic> References: <20210204211154.713523041@linutronix.de> <202102051148.WIj5O4Ry-lkp@intel.com> <20210208141957.GA18227@zn.tnic> <536a6b24-fadb-cb2a-8259-dadd3730c6ce@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <536a6b24-fadb-cb2a-8259-dadd3730c6ce@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 09, 2021 at 04:57:09PM +0800, Rong Chen wrote: > Thanks for the help, how can we identify the patches for tip tree, > could you please guide us? I guess something like: cat patch | ./scripts/get_maintainer.pl -m --no-r --no-l For a tip patch, it should give, among others: x86@kernel.org (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)) which is the tip ML. You'd need to play with this a bit to see what works best. Also, I'm wondering if it would make sense to have some special syntax to let the 0day bot know on which tree to apply the patches after scraping or to even be able to say: "do not test" when sending just an example patch which is not supposed to be used anyway and thus you don't have to waste infra cycles on it. HTH. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette