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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CB149C433EF for ; Tue, 14 Dec 2021 14:25:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=nJp9+rcHjDBOVrHqsqVO9EmOoKkDXF820H3J2UiDtro=; b=qHfgh4ifLhio5d RYZTEvoFlJzJ0+C/9FrrCXsMLN4X201S8UISQZj3lf661w/r92/4GOFyKyJUG+Mi9sa/G+cicxjaF ryxjGJawTavGoP7EEyFqyQMocXjosYBWfDFkBJ12WFLDnZgG86qGg6zLaGqXwjIdxtaA7LqKj1+Sd GLm7XnPG9bi57VZAnJpJ5WwfRzVd0jH6rWhKxwLo4CMdKAZrc7J3AZRH88uw9vaI5qhP9vwkQsS4d 3FEKI5QbSFk7uYZ/8+OrFJItsUMGZywhI9drh98rqebbyCPsLA9dQdMmSVMIb2/lCcwShmJI2Xgmk S0ysob2u/Dg7YWrwHnWA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mx8j9-00ENum-TQ; Tue, 14 Dec 2021 14:24:24 +0000 Received: from mail.skyhub.de ([2a01:4f8:190:11c2::b:1457]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mx8iy-00ENpK-FZ; Tue, 14 Dec 2021 14:24:16 +0000 Received: from zn.tnic (dslb-088-067-202-008.088.067.pools.vodafone-ip.de [88.67.202.8]) (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 86B1B1EC0513; Tue, 14 Dec 2021 15:24:03 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1639491843; 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=nztofOAHnNILlfJMC3O7KXR75xgQVsvCriH1qsLGzcc=; b=KmMHii+FF1pXrovIa4v2KZFHMm6frF/8tAoyVyS3H8VQCC+CWhisRFTtTEpEQ52e19DrT0 U13xGmpdvXwxPW/TKD9x8ZcwPt+0wyV75D4mdpbLYVC58WkSyKTN93KyWRNbWE8igxKpYA 2T7ET76iUgWJOFl+6bO6enxgbdzbIn4= Date: Tue, 14 Dec 2021 15:24:04 +0100 From: Borislav Petkov To: Baoquan He Cc: Zhen Lei , Thomas Gleixner , Ingo Molnar , x86@kernel.org, "H . Peter Anvin" , linux-kernel@vger.kernel.org, Dave Young , Vivek Goyal , Eric Biederman , kexec@lists.infradead.org, Catalin Marinas , Will Deacon , linux-arm-kernel@lists.infradead.org, Rob Herring , Frank Rowand , devicetree@vger.kernel.org, Jonathan Corbet , linux-doc@vger.kernel.org, Randy Dunlap , Feng Zhou , Kefeng Wang , Chen Zhou Subject: Re: [PATCH v17 03/10] x86: kdump: use macro CRASH_ADDR_LOW_MAX in functions reserve_crashkernel() Message-ID: References: <20211210065533.2023-1-thunder.leizhen@huawei.com> <20211210065533.2023-4-thunder.leizhen@huawei.com> <20211214085440.GA3023@MiWiFi-R3L-srv> <20211214095657.GB3023@MiWiFi-R3L-srv> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20211214095657.GB3023@MiWiFi-R3L-srv> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20211214_062412_744160_16259F41 X-CRM114-Status: GOOD ( 10.73 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Dec 14, 2021 at 05:56:57PM +0800, Baoquan He wrote: > Ah, OK, I see the new paragraph from you added in below commit. That is supposed to make it absolutely clear and explicit. There are other hints as to what a subsequent SOB means in that document already. Just the next section says: "The Signed-off-by: tag indicates that the signer was involved in the development of the patch, or that he/she was in the patch's delivery path." It wouldn't hurt if people would look at that doc from time to time - we end up referring to it on a daily basis. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel