public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Matthew Howell <matthew.howell@sealevel.com>
Cc: gregkh@linuxfoundation.org, 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: Tue, 5 Sep 2023 19:51:47 +0300	[thread overview]
Message-ID: <20230905165147.GS11662@atomide.com> (raw)
In-Reply-To: <79e44ee3-f4a0-6f3e-cb5d-dc2b7bd048fb@sealevel.com>

* Matthew Howell <matthew.howell@sealevel.com> [230905 16:43]:
> On Tue, 5 Sep 2023, Tony Lindgren wrote:
> > Maybe check if rmmod 8250_exar now somehow causes the following insmod
> > 8250_exar attempts to fail?
> 
> Could you clarify what you mean? It is at that stage that I normally see 
> the error in dmesg unless I have reverted the port id patch. In other 
> words, if I just load it as-is I get the error in question.
> 
> Do you mean to try loading the installed kernel module with insmod?
> If that is what you mean, I just tried loading the included binary with 
> insmod but did not get the error and it loaded correctly. I loaded it 
> with:
> 
> sudo insmod /usr/lib/modules/6.5.0-1-MANJARO/kernel/drivers/tty/serial/8250/8250_exar.ko.zst 

I meant maybe reloading 8250_exar fails. So the test I would do is build
build a plain v6.5 kernel, boot it, modprobe 8250_exar, rmmod 8250_exar,
and then again modprobe 8250_exar.

So maybe the first modprobe 8250_exar works after boot, but the second
modprobe 8250_exar won't?

> Do you see anything concerning or possibly incorrect with the way I am 
> building the 8250_exar module?

No I don't see how that would make a difference.

Regards,

Tony


  reply	other threads:[~2023-09-05 17:29 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 [this message]
2023-09-11 13:04                       ` Matthew Howell
2023-09-11 13:15                         ` Greg KH
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=20230905165147.GS11662@atomide.com \
    --to=tony@atomide.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=james.olson@sealevel.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=matthew.howell@sealevel.com \
    --cc=ryan.wenglarz@sealevel.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