From: Tony Lindgren <tony@atomide.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk,
"Paul Walmsley" <paul@pwsan.com>,
linux-omap@vger.kernel.org,
"Benoît Cousson" <bcousson@baylibre.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] ARM: OMAP2+: make omap44xx_sha0_hwmod and omap44xx_l3_main_2__des static
Date: Mon, 21 Oct 2019 10:37:27 -0700 [thread overview]
Message-ID: <20191021173727.GF5610@atomide.com> (raw)
In-Reply-To: <20191009085646.21755-2-ben.dooks@codethink.co.uk>
* Ben Dooks <ben.dooks@codethink.co.uk> [191009 01:57]:
> The omap44xx_sha0_hwmod and omap44xx_l3_main_2__des objects are
> not exported so make them static to avoid the following warnings:
>
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c:793:19: warning: symbol 'omap44xx_sha0_hwmod' was not declared. Should it be static?
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c:977:26: warning: symbol 'omap44xx_l3_main_2__des' was not declared. Should it be static?
Applying into omap-for-v5.5/soc thanks.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk,
"Paul Walmsley" <paul@pwsan.com>,
linux-omap@vger.kernel.org,
"Benoît Cousson" <bcousson@baylibre.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] ARM: OMAP2+: make omap44xx_sha0_hwmod and omap44xx_l3_main_2__des static
Date: Mon, 21 Oct 2019 10:37:27 -0700 [thread overview]
Message-ID: <20191021173727.GF5610@atomide.com> (raw)
In-Reply-To: <20191009085646.21755-2-ben.dooks@codethink.co.uk>
* Ben Dooks <ben.dooks@codethink.co.uk> [191009 01:57]:
> The omap44xx_sha0_hwmod and omap44xx_l3_main_2__des objects are
> not exported so make them static to avoid the following warnings:
>
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c:793:19: warning: symbol 'omap44xx_sha0_hwmod' was not declared. Should it be static?
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c:977:26: warning: symbol 'omap44xx_l3_main_2__des' was not declared. Should it be static?
Applying into omap-for-v5.5/soc thanks.
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-21 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 8:56 [PATCH 1/2] ARM: OMAP2+: make dra7xx_sha0_hwmod static Ben Dooks
2019-10-09 8:56 ` [PATCH 2/2] ARM: OMAP2+: make omap44xx_sha0_hwmod and omap44xx_l3_main_2__des static Ben Dooks
2019-10-21 17:37 ` Tony Lindgren [this message]
2019-10-21 17:37 ` Tony Lindgren
2019-10-21 17:35 ` [PATCH 1/2] ARM: OMAP2+: make dra7xx_sha0_hwmod static Tony Lindgren
2019-10-21 17:35 ` 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=20191021173727.GF5610@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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.