From: Greg KH <gregkh@linuxfoundation.org>
To: Hao Lee <haolee.swjtu@gmail.com>
Cc: jslaby@suse.com, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tty: serial: 8250: Fix type field in format string
Date: Mon, 29 Apr 2019 16:31:17 +0200 [thread overview]
Message-ID: <20190429143117.GA1474@kroah.com> (raw)
In-Reply-To: <20190427091943.GA3810@haolee.io>
On Sat, Apr 27, 2019 at 05:19:43PM +0800, Hao Lee wrote:
> The dev_dbg statement should print the value of uart.port.mapbase instead
> of its address. Besides that, uart.port.irq and uart.port.iotype are all
> unsigned types, so using %u is more appropriate.
>
> Signed-off-by: Hao Lee <haolee.swjtu@gmail.com>
> ---
> drivers/tty/serial/8250/8250_pnp.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/tty/serial/8250/8250_pnp.c b/drivers/tty/serial/8250/8250_pnp.c
> index 431e69a5a6a0..9dea11baf479 100644
> --- a/drivers/tty/serial/8250/8250_pnp.c
> +++ b/drivers/tty/serial/8250/8250_pnp.c
> @@ -462,8 +462,8 @@ serial_pnp_probe(struct pnp_dev *dev, const struct pnp_device_id *dev_id)
> return -ENODEV;
>
> dev_dbg(&dev->dev,
> - "Setup PNP port: port %lx, mem %pa, irq %d, type %d\n",
> - uart.port.iobase, &uart.port.mapbase,
> + "Setup PNP port: port %#lx, mem %#lx, irq %u, type %u\n",
> + uart.port.iobase, uart.port.mapbase,
> uart.port.irq, uart.port.iotype);
>
> if (flags & CIR_PORT) {
> --
> 2.14.5
This causes build warnings when applied, I'm having to drop it now.
Please be more careful, when submitting patches, always test-build them
first.
greg k-h
next prev parent reply other threads:[~2019-04-29 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 9:19 [PATCH v2] tty: serial: 8250: Fix type field in format string Hao Lee
2019-04-29 14:31 ` Greg KH [this message]
2019-04-29 16:23 ` Hao Lee
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=20190429143117.GA1474@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=haolee.swjtu@gmail.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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