From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: pic32: treat port as signed integer
Date: Fri, 11 Nov 2022 16:05:19 +0100 [thread overview]
Message-ID: <20221111150519.GE13465@alpha.franken.de> (raw)
In-Reply-To: <20221028132344.1993934-1-Jason@zx2c4.com>
On Fri, Oct 28, 2022 at 03:23:44PM +0200, Jason A. Donenfeld wrote:
> get_port_from_cmdline() returns an int, yet is assigned to a char, which
> is wrong in its own right, but also, with char becoming unsigned, this
> poses problems, because -1 is used as an error value. Further
> complicating things, fw_init_early_console() is only ever called with a
> -1 argument. Fix this up by removing the unused argument from
> fw_init_early_console() and treating port as a proper signed integer.
>
> Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> ---
> Thomas - this is part of the -funsigned-char work I've been accumulating
> in my unsigned-char branch. If you want to take this as a fix for 6.1,
> go ahead. Otherwise, Linus asked me to keep the 6.2 unsigned-char
> patches together in my branch, so I'll take this, pending your Ack.
> -Jason
>
> arch/mips/include/asm/fw/fw.h | 2 +-
> arch/mips/pic32/pic32mzda/early_console.c | 13 ++++++-------
> arch/mips/pic32/pic32mzda/init.c | 2 +-
> 3 files changed, 8 insertions(+), 9 deletions(-)
applied to mips-fixes.
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:[~2022-11-11 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 13:23 [PATCH] MIPS: pic32: treat port as signed integer Jason A. Donenfeld
2022-11-11 15:05 ` 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=20221111150519.GE13465@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--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