From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-mips@linux-mips.org, "Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"open list:BROADCOM BCM47XX MIPS ARCHITECTURE"
<linux-mips@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] firmware: bcm47xx_sprom: Fix -Wmissing-prototypes warnings
Date: Mon, 17 Aug 2020 13:53:08 +0200 [thread overview]
Message-ID: <20200817115308.GA4796@alpha.franken.de> (raw)
In-Reply-To: <20200726041521.5398-1-f.fainelli@gmail.com>
On Sat, Jul 25, 2020 at 09:15:19PM -0700, Florian Fainelli wrote:
> Hi Thomas,
>
> This patch series fixes W=1 -Wmissing-prototypes warnings for the
> bcm47xx_sprom.c firmware file.
>
> Thanks!
>
> Florian Fainelli (2):
> firmware: bcm47xx_sprom: Fix -Wmissing-prototypes warnings
> MIPS: BCM47xx: Include bcm47xx_sprom.h
>
> arch/mips/include/asm/mach-bcm47xx/bcm47xx.h | 4 +---
> drivers/firmware/broadcom/bcm47xx_sprom.c | 1 +
> include/linux/bcm47xx_sprom.h | 10 ++++++++++
> 3 files changed, 12 insertions(+), 3 deletions(-)
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-08-17 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 4:15 [PATCH 0/2] firmware: bcm47xx_sprom: Fix -Wmissing-prototypes warnings Florian Fainelli
2020-07-26 4:15 ` [PATCH 1/2] " Florian Fainelli
2020-07-26 4:15 ` [PATCH 2/2] MIPS: BCM47xx: Include bcm47xx_sprom.h Florian Fainelli
2020-08-07 18:37 ` [PATCH 0/2] firmware: bcm47xx_sprom: Fix -Wmissing-prototypes warnings Florian Fainelli
2020-08-12 14:52 ` Thomas Bogendoerfer
2020-08-17 11:53 ` Thomas Bogendoerfer [this message]
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=20200817115308.GA4796@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mips@vger.kernel.org \
--cc=zajec5@gmail.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.