Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp729907ybt; Fri, 19 Jun 2020 12:12:10 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyf5xCVPoG6gkgLY/tdwiSeVBc5xwXRi9V579plBHWKs2eNUFqLoOo9YYZwnu7ukCzY74U2 X-Received: by 2002:a17:906:2615:: with SMTP id h21mr4942981ejc.84.1592593930508; Fri, 19 Jun 2020 12:12:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592593930; cv=none; d=google.com; s=arc-20160816; b=P2sJ6UERNPC2aWkvsoTnLX/s6Y6R0DUIzAfveNsKUw2IGsnZFVIQ64Iwmgt8lX8+Ah 9zPXq1j5QPTT93EjZGBIfvrbkQvBUDGsWS50SyGCpJIO1NxZqdIM2v211JF0oL9Tm45+ o12dgCan4RSLQXFiy9GWJDd+m0quxWpdkSl8UshVkndMOawQfw/2FTwtyELpJgMwv1fD O3cjrAevqKdlXEYb1dXl9+pTYJxOODACnR/gYz1dOH4q/CQAia/v9A+HqK9G+JndrQST 63xSyjIfmjyu8Y4TekbsY6FvPKT6WG5qEkHQ4ZosEBLva80QgoxebSP3CMFHICWEIRbS b1Sg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=EJ2H/fVddiAPK6hXHAtQLifLDsxa0nRqV7Ub9F0/6dA=; b=Brm+5R3ddOEg88SJYoFT9eeoSpjytruFDq7wAZ7iG0V5fXFdaGDNQvTWvHCUSZvDyA DECvNtpnNKaB4PBwNGM0fo3RdOKOv+dOVuAiQU+JudvKuhhowJ9WaPrjYJE0P4XyTVm9 WT+4UPUSRud09BnEDDwUysQwXaiKNTuz5ZfLQZnaQ9K6GLlVzmo1n//ATOyRQFoJNm33 +ULEUxtwpfyi+MYXmrQcZNgKLbQig2ICQeLYk89JIbJqEPoSwITxPppD/9wRiWgpfiHi API0+LVJTMdVYtXocudWYJVD/MHHP85JY2egNmBuyI5YgfdDbRWVM+/pgUWHCZJL5FLf upcQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s21si4130483ejz.9.2020.06.19.12.11.48; Fri, 19 Jun 2020 12:12:10 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733170AbgFSObF (ORCPT + 99 others); Fri, 19 Jun 2020 10:31:05 -0400 Received: from mail-qv1-f65.google.com ([209.85.219.65]:36519 "EHLO mail-qv1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726594AbgFSObD (ORCPT ); Fri, 19 Jun 2020 10:31:03 -0400 Received: by mail-qv1-f65.google.com with SMTP id x16so4540253qvr.3 for ; Fri, 19 Jun 2020 07:31:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=EJ2H/fVddiAPK6hXHAtQLifLDsxa0nRqV7Ub9F0/6dA=; b=BzvkDu2m1ekzExLNWtg8GFpN1K72nnVMOjw3cC9rvR+v1X0nY4aYeTQlYMMounSg2M my+9E1t6SCQjfdVPqeN2TxuF0m53+/L0Fpe2i0tD/Vk5rcAxIkSQfpcKDKpy+kfP2Heb stgkwSJe0if/ORJdjvAcEY3V1ltjJG5+cxOKrqPvrOJRDa4x+v9Qwy3ZpdzSWh5GG68N c9UlUKtOHzCgVS+xyUCSGoSYvr/W77Gq0vKsrybKsm3EnLAOxWJt6VGLu5WNa3BFRQHZ VaSVn52674XeFdUFDzUB7L8dm+D8eZt7ODgxU1Bh6YhA3YbKXHIp3DVKMD3AllIolZJd 9AIQ== X-Gm-Message-State: AOAM532i+i3gUth0N8zjEBTN4mgSYx7BbfLXH+RDFm0d7/aGrverwT2p DCzarUDLZh8lwr2GUyzx20Uf8NA= X-Received: by 2002:a0c:efcf:: with SMTP id a15mr9180329qvt.108.1592577061579; Fri, 19 Jun 2020 07:31:01 -0700 (PDT) Received: from bill-the-cat.local (2606-a000-1401-8080-8c25-1271-b281-e614.inf6.spectrum.com. [2606:a000:1401:8080:8c25:1271:b281:e614]) by smtp.gmail.com with ESMTPSA id u1sm6271677qkj.5.2020.06.19.07.31.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 19 Jun 2020 07:31:00 -0700 (PDT) From: Tom Rini To: linux-kernel@vger.kernel.org Cc: Andrew Morton , Borislav Petkov , Dominik Brodowski , "H . Peter Anvin" , "Ronald G . Minnich" Subject: [PATCH] initrd: Remove erroneous comment Date: Fri, 19 Jun 2020 10:30:56 -0400 Message-Id: <20200619143056.24538-1-trini@konsulko.com> X-Mailer: git-send-email 2.17.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Most architectures have been passing the location of an initrd via the initrd= option since their inception. Remove the comment as it's both wrong and unrelated to the commit that introduced it. Fixes: 694cfd87b0c8 ("x86/setup: Add an initrdmem= option to specify initrd physical address") Cc: Andrew Morton Cc: Borislav Petkov Cc: Dominik Brodowski Cc: H. Peter Anvin (Intel) Cc: Ronald G. Minnich Signed-off-by: Tom Rini --- For a bit more context, I assume there's been some confusion between "initrd" being a keyword in things like extlinux.conf and also that for quite a long time now initrd information is passed via device tree and not the command line on relevant architectures. But it's still true that it's been a valid command line option to the kernel since the 90s. It's just the case that in 2018 the code was consolidated from under arch/ and in to this file. --- init/do_mounts_initrd.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/init/do_mounts_initrd.c b/init/do_mounts_initrd.c index d72beda824aa..53314d7da4be 100644 --- a/init/do_mounts_initrd.c +++ b/init/do_mounts_initrd.c @@ -45,11 +45,6 @@ static int __init early_initrdmem(char *p) } early_param("initrdmem", early_initrdmem); -/* - * This is here as the initrd keyword has been in use since 11/2018 - * on ARM, PowerPC, and MIPS. - * It should not be; it is reserved for bootloaders. - */ static int __init early_initrd(char *p) { return early_initrdmem(p); -- 2.17.1