From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial <linux-serial@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] tty/serial: Sort drivers in makefile
Date: Wed, 13 Sep 2023 13:36:30 +0300 (EEST) [thread overview]
Message-ID: <e25ef4f-48bb-eeff-f181-794afe716a81@linux.intel.com> (raw)
In-Reply-To: <e74982c0-4942-1c46-1c53-6dd6e7677373@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
On Wed, 13 Sep 2023, Jiri Slaby wrote:
> On 12. 09. 23, 12:35, Ilpo Järvinen wrote:
> > Sort drivers in alphabetic order in Makefile to make it easier to find
> > the correct line. In case the CONFIG and filenames disagree, sort using
> > the filename (but ignoring "serial" prefixes).
>
> Overall looks good.
>
> I just want to make sure you considered the below, as you don't say explicitly
> in the commit log.
>
> The order in the makefile defines the link order. So built-in drivers are
> loaded in that order. So are you sure your patch doesn't change order of some
> drivers which need to be in a specific order?
Thanks for taking a look.
I limited the ordering to non-library like "leaf" driver files so it
should be safe. Except for 8250_early that was in middle of drivers so
I moved it before the driver section but that doesn't alter anything
important AFAICT.
In any case, I double-checked this again and only thing I found out is
that for some reason SERIAL_8250_EXAR depends on 8250_PCI but nothing uses
the 4 functions 8250_pci.c EXPORTs (which I'll address shortly).
--
i.
prev parent reply other threads:[~2023-09-13 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 10:35 [PATCH 1/2] tty/serial: Sort drivers in makefile Ilpo Järvinen
2023-09-12 10:35 ` [PATCH 2/2] tty/serial: 8250: Sort drivers in Makefile Ilpo Järvinen
2023-09-13 5:29 ` [PATCH 1/2] tty/serial: Sort drivers in makefile Jiri Slaby
2023-09-13 10:36 ` Ilpo Järvinen [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=e25ef4f-48bb-eeff-f181-794afe716a81@linux.intel.com \
--to=ilpo.jarvinen@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