From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v1 0/5] serial: 8250_exar: A few updates to the driver
Date: Wed, 14 Feb 2024 19:09:33 +0200 [thread overview]
Message-ID: <20240214171044.3551032-1-andriy.shevchenko@linux.intel.com> (raw)
A few updates to the 8250 Exar driver as per new in-kernel APIs
appeared.
Andy Shevchenko (5):
serial: 8250_exar: Clear interrupts before registering handler
serial: 8250_exar: Use generic function to set firmware node
serial: 8250_exar: switch to DEFINE_SIMPLE_DEV_PM_OPS()
serial: 8250_exar: Use 8250 PCI library to map and assign resources
serial: 8250_exar: Don't use "proxy" headers
drivers/tty/serial/8250/8250_exar.c | 43 ++++++++++++++++-------------
drivers/tty/serial/8250/Kconfig | 1 +
2 files changed, 25 insertions(+), 19 deletions(-)
--
2.43.0.rc1.1.gbec44491f096
next reply other threads:[~2024-02-14 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 17:09 Andy Shevchenko [this message]
2024-02-14 17:09 ` [PATCH v1 1/5] serial: 8250_exar: Clear interrupts before registering handler Andy Shevchenko
2024-02-14 17:09 ` [PATCH v1 2/5] serial: 8250_exar: Use generic function to set firmware node Andy Shevchenko
2024-02-14 17:09 ` [PATCH v1 3/5] serial: 8250_exar: switch to DEFINE_SIMPLE_DEV_PM_OPS() Andy Shevchenko
2024-02-14 17:09 ` [PATCH v1 4/5] serial: 8250_exar: Use 8250 PCI library to map and assign resources Andy Shevchenko
2024-02-17 4:44 ` kernel test robot
2024-02-17 16:44 ` Greg Kroah-Hartman
2024-02-19 13:29 ` Andy Shevchenko
2024-02-14 17:09 ` [PATCH v1 5/5] serial: 8250_exar: Don't use "proxy" headers Andy Shevchenko
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=20240214171044.3551032-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--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