From: Jiri Slaby <jirislaby@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v1 1/1] serial: 8250_ce4100: Fix CONFIG_SERIAL_8250=n build
Date: Wed, 16 Jul 2025 12:43:42 +0200 [thread overview]
Message-ID: <7d3afa64-2bd4-4710-8c16-2a2815d5b644@kernel.org> (raw)
In-Reply-To: <aHd-urMzXlOJPDAm@smile.fi.intel.com>
On 16. 07. 25, 12:28, Andy Shevchenko wrote:
> On Wed, Jul 16, 2025 at 12:14:23PM +0200, Jiri Slaby wrote:
>> On 16. 07. 25, 11:44, Andy Shevchenko wrote:
>>> On i386, when
>>>
>>> CONFIG_X86_INTEL_CE=y
>>> # CONFIG_SERIAL_8250 is not set
>>>
>>> will try to compile the driver and use the stub simultaneously.
>>> This breaks the build. Fix it by making sure that the driver
>>> compiles only when CONFIG_SERIAL_8250 is also enabled.
>
> ...
>
>>> +ifneq ($(CONFIG_SERIAL_8250),)
>>
>> Why not ifdef CONFIG_SERIAL_8250 then?
>
> $ git grep -n '^ifn\?eq .*CONFIG_' | wc -l
> 427
> $ git grep -n '^ifdef CONFIG_' | wc -l
> 431
>
> Is there a preference in serial drivers?
The simpler to read/understand -- the latter.
>> Also, what happens if 8250=m and X86_INTEL_CE=y?
>
> So, in such a case if somebody wants to use UART, it will go crazy due to
> missed workaround applied. BUT, this is preexisted issue and not related
> (directly) to this fix. Perhaps we can combine both with
>
> ifeq ($(CONFIG_SERIAL_8250),y)
>
> and add two Fixes tags.
+1 makes sense to me. Or introduce a Kconfig entry to handle the deps...
thanks,
--
js
suse labs
prev parent reply other threads:[~2025-07-16 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 9:44 Andy Shevchenko
2025-07-16 10:14 ` Jiri Slaby
2025-07-16 10:28 ` Andy Shevchenko
2025-07-16 10:43 ` Jiri Slaby [this message]
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=7d3afa64-2bd4-4710-8c16-2a2815d5b644@kernel.org \
--to=jirislaby@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®