From: <kexybiscuit@aosc.io>
To: "'Greg Kroah-Hartman'" <gregkh@linuxfoundation.org>
Cc: "'Jiri Slaby'" <jirislaby@kernel.org>,
"'Serge Semin'" <fancer.lancer@gmail.com>,
"'Thomas Bogendoerfer'" <tsbogend@alpha.franken.de>,
<linux-kernel@vger.kernel.org>, <linux-serial@vger.kernel.org>
Subject: RE: [PATCH] tty: mips_ejtag_fdc: Fix another passing incompatible pointer type warning
Date: Sat, 11 Jan 2025 17:14:49 +0800 [thread overview]
Message-ID: <029c01db6409$46e88b50$d4b9a1f0$@aosc.io> (raw)
In-Reply-To: <2025011159-whole-undivided-26e9@gregkh>
Cool, I'll search the list before sending next time, thanks!
-----Original Message-----
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Sent: Saturday, January 11, 2025 1:52 PM
To: Kexy Biscuit <kexybiscuit@aosc.io>
Cc: Jiri Slaby <jirislaby@kernel.org>; Serge Semin <fancer.lancer@gmail.com>; Thomas Bogendoerfer <tsbogend@alpha.franken.de>; linux-kernel@vger.kernel.org; linux-serial@vger.kernel.org
Subject: Re: [PATCH] tty: mips_ejtag_fdc: Fix another passing incompatible pointer type warning
On Sat, Jan 11, 2025 at 01:38:51AM +0800, Kexy Biscuit wrote:
> mips_ejtag_fdc_encode() method was changed to accept u8** since
> ce7cbd9a6c81, but not all occurrences were changed to adapt it.
>
> Some of the warnings or errors was fixed in a previous commit, this
> commit fixes one more of them.
>
> drivers/tty/mips_ejtag_fdc.c: In function ‘kgdbfdc_push_one’:
> drivers/tty/mips_ejtag_fdc.c:1224:38: error: passing argument 1 of ‘mips_ejtag_fdc_encode’ from incompatible pointer type [-Werror=incompatible-pointer-types]
> 1224 | word = mips_ejtag_fdc_encode(bufs, &kgdbfdc_wbuflen, 1);
> | ^~~~
> | |
> | const char **
> drivers/tty/mips_ejtag_fdc.c:216:57: note: expected ‘const u8 **’ {aka ‘const unsigned char **’} but argument is of type ‘const char **’
> 216 | static struct fdc_word mips_ejtag_fdc_encode(const u8 **ptrs,
> | ~~~~~~~~~~~^~~~
>
> Fixes: ce7cbd9a6c81 ("tty: mips_ejtag_fdc: use u8 for character pointers")
> Fixes: 188942f05ce4 ("tty: mips_ejtag_fdc: Fix passing incompatible pointer type warning")
> Signed-off-by: Kexy Biscuit <kexybiscuit@aosc.io>
> ---
> drivers/tty/mips_ejtag_fdc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/mips_ejtag_fdc.c b/drivers/tty/mips_ejtag_fdc.c
> index afbf7738c7c47c3377560a3288fa95083dd1c6b0..1cc775e74f92d2c5e7a7b4bb500ff2ae758da8e0 100644
> --- a/drivers/tty/mips_ejtag_fdc.c
> +++ b/drivers/tty/mips_ejtag_fdc.c
> @@ -1215,7 +1215,7 @@ static int kgdbfdc_read_char(void)
> /* push an FDC word from write buffer to TX FIFO */
> static void kgdbfdc_push_one(void)
> {
> - const char *bufs[1] = { kgdbfdc_wbuf };
> + const u8 *bufs[1] = { kgdbfdc_wbuf };
> struct fdc_word word;
> void __iomem *regs;
> unsigned int i;
Jiri beat you to it yesterday:
https://lore.kernel.org/r/20250110115228.603980-1-jirislaby@kernel.org
prev parent reply other threads:[~2025-01-11 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 17:38 Kexy Biscuit
2025-01-11 5:52 ` Greg Kroah-Hartman
2025-01-11 9:14 ` kexybiscuit [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='029c01db6409$46e88b50$d4b9a1f0$@aosc.io' \
--to=kexybiscuit@aosc.io \
--cc=fancer.lancer@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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
all inboxes | Powered by JetHome®