Linux Serial subsystem development
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Tobias Klauser <tklauser@distanz.ch>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	Antony Pavlov <antonynpavlov@gmail.com>
Subject: [PATCH] tty/serial: altera_uart: use more informative labels in /proc/interrupts
Date: Sun, 17 Dec 2023 22:56:01 +0300	[thread overview]
Message-ID: <20231217195601.236002-1-antonynpavlov@gmail.com> (raw)

Prior to this patch:

~# cat /proc/interrupts
...
 40:        123          0     GIC-0  72 Level     altera_uart
 41:          9          0     GIC-0  73 Level     altera_uart

After this patch:

~# cat /proc/interrupts
...
 40:          6          0     GIC-0  72 Level     ff200100.fpga-uart0
 41:         28          0     GIC-0  73 Level     ff200200.fpga-uart1

Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
---
 drivers/tty/serial/altera_uart.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/tty/serial/altera_uart.c b/drivers/tty/serial/altera_uart.c
index 77835ac68df26..7e28928e58787 100644
--- a/drivers/tty/serial/altera_uart.c
+++ b/drivers/tty/serial/altera_uart.c
@@ -305,7 +305,7 @@ static int altera_uart_startup(struct uart_port *port)
 		int ret;
 
 		ret = request_irq(port->irq, altera_uart_interrupt, 0,
-				DRV_NAME, port);
+				dev_name(port->dev), port);
 		if (ret) {
 			pr_err(DRV_NAME ": unable to attach Altera UART %d "
 			       "interrupt vector=%d\n", port->line, port->irq);
-- 
2.39.0


             reply	other threads:[~2023-12-17 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-17 19:56 Antony Pavlov [this message]
2023-12-19 11:10 ` [PATCH] tty/serial: altera_uart: use more informative labels in /proc/interrupts Tobias Klauser

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=20231217195601.236002-1-antonynpavlov@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=tklauser@distanz.ch \
    /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