From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [PATCH v1 4/5] serial: 8250_exar: Use 8250 PCI library to map and assign resources
Date: Mon, 19 Feb 2024 15:29:02 +0200 [thread overview]
Message-ID: <ZdNXnoQ4vEr4irIm@smile.fi.intel.com> (raw)
In-Reply-To: <2024021723-spellbind-citadel-d2c1@gregkh>
On Sat, Feb 17, 2024 at 05:44:31PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Feb 14, 2024 at 07:09:37PM +0200, Andy Shevchenko wrote:
> > 8250 PCI library provides a common code to map and assign resources.
> > Use it in order to deduplicate existing code and support IO port
> > variants.
>
> Looks like you have a build error :(
Indeed, somehow I messed up with branches I have compiled.
v2 will be issued soon.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-02-19 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 17:09 [PATCH v1 0/5] serial: 8250_exar: A few updates to the driver Andy Shevchenko
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 [this message]
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=ZdNXnoQ4vEr4irIm@smile.fi.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