From: Mike Rapoport <rppt@linux.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Dinh Nguyen <dinguyen@kernel.org>,
Andreas Oetken <andreas.oetken@siemens.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: Re: [PATCH] NIOS2: setup.c: drop unused variable 'dram_start'
Date: Sun, 26 Sep 2021 08:29:41 +0300 [thread overview]
Message-ID: <YVAFRdc/DWN0scc7@linux.ibm.com> (raw)
In-Reply-To: <20210924210525.7053-1-rdunlap@infradead.org>
On Fri, Sep 24, 2021 at 02:05:25PM -0700, Randy Dunlap wrote:
> This is a nuisance when CONFIG_WERROR is set, so drop the variable
> declaration since the code that used it was removed.
>
> ../arch/nios2/kernel/setup.c: In function 'setup_arch':
> ../arch/nios2/kernel/setup.c:152:13: warning: unused variable 'dram_start' [-Wunused-variable]
> 152 | int dram_start;
>
> Fixes: 7f7bc20bc41a ("nios2: Don't use _end for calculating min_low_pfn")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Cc: Dinh Nguyen <dinguyen@kernel.org>
> Cc: Andreas Oetken <andreas.oetken@siemens.com>
> Cc: Mike Rapoport <rppt@linux.vnet.ibm.com>
Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>
> ---
> arch/nios2/kernel/setup.c | 2 --
> 1 file changed, 2 deletions(-)
>
> --- linux-next-20210917.orig/arch/nios2/kernel/setup.c
> +++ linux-next-20210917/arch/nios2/kernel/setup.c
> @@ -149,8 +149,6 @@ static void __init find_limits(unsigned
>
> void __init setup_arch(char **cmdline_p)
> {
> - int dram_start;
> -
> console_verbose();
>
> memory_start = memblock_start_of_DRAM();
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2021-09-26 5:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 21:05 [PATCH] NIOS2: setup.c: drop unused variable 'dram_start' Randy Dunlap
2021-09-26 5:29 ` Mike Rapoport [this message]
2021-09-27 13:40 ` Dinh Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YVAFRdc/DWN0scc7@linux.ibm.com \
--to=rppt@linux.ibm.com \
--cc=andreas.oetken@siemens.com \
--cc=dinguyen@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rdunlap@infradead.org \
--cc=rppt@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox