From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Woody Suwalski <terraluna977@gmail.com>
Cc: Guanbing Huang <albanhuang@outlook.com>,
gregkh@linuxfoundation.org, rafael.j.wysocki@intel.com,
linux-acpi@vger.kernel.org, tony@atomide.com,
john.ogness@linutronix.de, yangyicong@hisilicon.com,
jirislaby@kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, lvjianmin@loongson.cn,
albanhuang@tencent.com, tombinfan@tencent.com
Subject: Re: Kernel 6.10-rc1 b,Build error with [PATCH v5 2/3] serial: port: Add support of PNP IRQ
Date: Mon, 27 May 2024 23:15:34 +0300 [thread overview]
Message-ID: <ZlTp5lGiT3pNF_di@smile.fi.intel.com> (raw)
In-Reply-To: <cc8a93b2-2504-9754-e26c-5d5c3bd1265c@gmail.com>
On Mon, May 27, 2024 at 03:44:42PM -0400, Woody Suwalski wrote:
> Guanbing Huang wrote:
> > From: Guanbing Huang <albanhuang@tencent.com>
> >
> > The function __uart_read_properties doesn't cover PNP devices, so add IRQ
> > processing for PNP devices in the branch.
...
> > #include <linux/property.h>
> > #include <linux/serial_core.h>
> > #include <linux/spinlock.h>
> > @@ -221,7 +222,11 @@ static int __uart_read_properties(struct uart_port *port, bool use_defaults)
> > if (dev_is_platform(dev))
> > ret = platform_get_irq(to_platform_device(dev), 0);
> > - else
> > + else if (dev_is_pnp(dev)) {
> > + ret = pnp_irq(to_pnp_dev(dev), 0);
> > + if (ret < 0)
> > + ret = -ENXIO;
> > + } else
> > ret = fwnode_irq_get(dev_fwnode(dev), 0);
> > if (ret == -EPROBE_DEFER)
> > return ret;
>
> Hello all, trying to build 6.10-rc1 fails for me in serial_base.o:
> CALL scripts/checksyscalls.sh
> DESCEND objtool
> INSTALL libsubcmd_headers
> CC [M] drivers/tty/serial/serial_port.o
> LD [M] drivers/tty/serial/serial_base.o
> MODPOST Module.symvers
> ERROR: modpost: "pnp_bus_type" [drivers/tty/serial/serial_base.ko]
> undefined!
> make[2]: *** [scripts/Makefile.modpost:145: Module.symvers] Error 1
> make[1]: ***
> [/woody/src/kernels/linux-6.10-pingu/work/linux-6.10/Makefile:1892: modpost]
> Error 2
> make: *** [Makefile:246: __sub-make] Error 2
>
> Reversing the patch "fixes" the problem :-(
> I am building on a Debian bookworm system, gcc 12.2
>
> Any suggestions how to make it work?
Yes, I will send a patch soon. Thanks for the report!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-05-27 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1712472167.git.albanhuang@tencent.com>
2024-04-08 3:36 ` [PATCH v5 1/3] PNP: Add dev_is_pnp() macro Guanbing Huang
2024-04-08 3:36 ` [PATCH v5 2/3] serial: port: Add support of PNP IRQ to __uart_read_properties() Guanbing Huang
2024-05-27 19:44 ` Kernel 6.10-rc1 b,Build error with [PATCH v5 2/3] serial: port: Add support of PNP IRQ Woody Suwalski
2024-05-27 20:15 ` Andy Shevchenko [this message]
2024-04-08 3:36 ` [PATCH v5 3/3] serial: 8250_pnp: Support configurable reg shift property Guanbing Huang
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=ZlTp5lGiT3pNF_di@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=albanhuang@outlook.com \
--cc=albanhuang@tencent.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lvjianmin@loongson.cn \
--cc=rafael.j.wysocki@intel.com \
--cc=terraluna977@gmail.com \
--cc=tombinfan@tencent.com \
--cc=tony@atomide.com \
--cc=yangyicong@hisilicon.com \
/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