All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Yongqiang Liu <liuyongqiang13@huawei.com>
Cc: linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org,
	linux-omap@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH -next] ARM: OMAP2+: Fix build warning when mmc_omap is not built
Date: Tue, 18 May 2021 09:27:51 +0300	[thread overview]
Message-ID: <YKNeZ/uZ7fOgTE8d@atomide.com> (raw)
In-Reply-To: <20210401131533.998767-1-liuyongqiang13@huawei.com>

* Yongqiang Liu <liuyongqiang13@huawei.com> [210401 16:09]:
> GCC reports the following warning with W=1:
> 
> arch/arm/mach-omap2/board-n8x0.c:325:19: warning:
> variable 'index' set but not used [-Wunused-but-set-variable]
> 325 |  int bit, *openp, index;
>     |                   ^~~~~
> 
> Fix this by moving CONFIG_MMC_OMAP to cover the rest codes
> in the n8x0_mmc_callback().

Thanks applying into fixes.

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Yongqiang Liu <liuyongqiang13@huawei.com>
Cc: linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org,
	linux-omap@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH -next] ARM: OMAP2+: Fix build warning when mmc_omap is not built
Date: Tue, 18 May 2021 09:27:51 +0300	[thread overview]
Message-ID: <YKNeZ/uZ7fOgTE8d@atomide.com> (raw)
In-Reply-To: <20210401131533.998767-1-liuyongqiang13@huawei.com>

* Yongqiang Liu <liuyongqiang13@huawei.com> [210401 16:09]:
> GCC reports the following warning with W=1:
> 
> arch/arm/mach-omap2/board-n8x0.c:325:19: warning:
> variable 'index' set but not used [-Wunused-but-set-variable]
> 325 |  int bit, *openp, index;
>     |                   ^~~~~
> 
> Fix this by moving CONFIG_MMC_OMAP to cover the rest codes
> in the n8x0_mmc_callback().

Thanks applying into fixes.

Tony

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-05-18  6:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 13:15 [PATCH -next] ARM: OMAP2+: Fix build warning when mmc_omap is not built Yongqiang Liu
2021-04-01 13:15 ` Yongqiang Liu
2021-05-18  6:27 ` Tony Lindgren [this message]
2021-05-18  6:27   ` Tony Lindgren

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=YKNeZ/uZ7fOgTE8d@atomide.com \
    --to=tony@atomide.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=liuyongqiang13@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.