From: Greg KH <gregkh@linuxfoundation.org>
To: Matthew Howell <matthew.howell@sealevel.com>
Cc: Tony Lindgren <tony@atomide.com>,
linux-serial@vger.kernel.org, ryan.wenglarz@sealevel.com,
james.olson@sealevel.com
Subject: Re: [PATCH] serial: Revert serial: core: Fix serial core port id to not use port->line
Date: Mon, 11 Sep 2023 15:15:42 +0200 [thread overview]
Message-ID: <2023091154-gallery-janitor-6ae3@gregkh> (raw)
In-Reply-To: <73817d5-cab-341-be76-ee9d565df57@sealevel.com>
On Mon, Sep 11, 2023 at 09:04:14AM -0400, Matthew Howell wrote:
> So it seems like this might not be an issue for typical 'users' of the
> kernel, but may impact people who need to build and load 8250_exar
> manually for whatever reason, unless I am just building the module
> incorrectly somehow.
Yes, Linux does not support building a module against one source
tree/configuration and attempting to load it into a different kernel at
all. You are lucky that this was the only thing that broke :)
Thanks for the testing and letting us know that all is good with the
tree as-is.
greg k-h
next prev parent reply other threads:[~2023-09-11 21:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 20:41 [PATCH] serial: Revert serial: core: Fix serial core port id to not use port->line Matthew Howell
2023-08-29 3:52 ` Tony Lindgren
2023-08-29 13:42 ` Matthew Howell
2023-08-29 20:15 ` Tony Lindgren
2023-08-31 14:58 ` Matthew Howell
2023-09-01 4:47 ` Tony Lindgren
2023-09-01 18:48 ` Matthew Howell
2023-09-02 4:34 ` Tony Lindgren
[not found] ` <c4b1db31-7814-0d22-36de-a7e6f117d89c@sealevel.com>
2023-09-05 15:55 ` Tony Lindgren
2023-09-05 16:43 ` Matthew Howell
2023-09-05 16:51 ` Tony Lindgren
2023-09-11 13:04 ` Matthew Howell
2023-09-11 13:15 ` Greg KH [this message]
2023-09-11 13:58 ` Matthew Howell
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=2023091154-gallery-janitor-6ae3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=james.olson@sealevel.com \
--cc=linux-serial@vger.kernel.org \
--cc=matthew.howell@sealevel.com \
--cc=ryan.wenglarz@sealevel.com \
--cc=tony@atomide.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