From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Daniel González Cabanelas" <dgcbueu@gmail.com>
Cc: f.fainelli@gmail.com, bcm-kernel-feedback-list@broadcom.com,
linux-mips@vger.kernel.org
Subject: Re: [PATCH] MIPS: BCM63XX: fix BCM6358 GPIO count
Date: Mon, 25 May 2020 15:29:31 +0200 [thread overview]
Message-ID: <20200525132931.GA12983@alpha.franken.de> (raw)
In-Reply-To: <4452917.ZOZUicq8Ig@tool>
On Sun, May 24, 2020 at 08:59:53PM +0200, Daniel González Cabanelas wrote:
> The BCM6358 SoC has only 38 available GPIOs. Fix it.
>
> Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
> ---
> arch/mips/include/asm/mach-bcm63xx/bcm63xx_gpio.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
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-05-25 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 18:59 [PATCH] MIPS: BCM63XX: fix BCM6358 GPIO count Daniel González Cabanelas
2020-05-25 13:29 ` 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=20200525132931.GA12983@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dgcbueu@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=linux-mips@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).