Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752451AbbHZRZA (ORCPT ); Wed, 26 Aug 2015 13:25:00 -0400 Received: from mail-wi0-f170.google.com ([209.85.212.170]:34665 "EHLO mail-wi0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751840AbbHZRY6 (ORCPT ); Wed, 26 Aug 2015 13:24:58 -0400 Date: Wed, 26 Aug 2015 18:24:55 +0100 From: Matt Fleming To: Leif Lindholm Cc: linux-efi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, matt.fleming@intel.com, ard.biesheuvel@linaro.org, msalter@redhat.com Subject: Re: [PATCH 2/3] arm64: use core efi=debug instead of uefi_debug command line parameter Message-ID: <20150826172455.GB2837@codeblueprint.co.uk> References: <1440595498-30630-1-git-send-email-leif.lindholm@linaro.org> <1440595498-30630-3-git-send-email-leif.lindholm@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1440595498-30630-3-git-send-email-leif.lindholm@linaro.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 920 Lines: 23 On Wed, 26 Aug, at 02:24:57PM, Leif Lindholm wrote: > Now that we have an efi=debug command line option in the core code, use > this instead of the arm64-specific uefi_debug option. > > Signed-off-by: Leif Lindholm > --- > Documentation/arm/uefi.txt | 2 -- > arch/arm64/kernel/efi.c | 19 +++++-------------- > 2 files changed, 5 insertions(+), 16 deletions(-) Are there no concerns with backwards-compatibility here? I expected this patch to internally convert uefi_debug to efi=debug if old boot loaders, kernel config, etc specify it. Is that something that can be safely ignored? -- Matt Fleming, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/