public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Josh Boyer <jwboyer@redhat.com>
Cc: Jiri Slaby <jslaby@suse.cz>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 8250.nr_uarts broken in 3.7
Date: Fri, 8 Mar 2013 07:12:42 +0800	[thread overview]
Message-ID: <20130307231242.GC4280@kroah.com> (raw)
In-Reply-To: <20130307211426.GI13719@hansolo.jdub.homelinux.org>

On Thu, Mar 07, 2013 at 04:14:27PM -0500, Josh Boyer wrote:
> On Thu, Mar 07, 2013 at 02:10:05PM -0500, Josh Boyer wrote:
> > On Thu, Mar 07, 2013 at 08:07:23PM +0100, Jiri Slaby wrote:
> > > On 03/07/2013 07:56 PM, Josh Boyer wrote:
> > > > commit 835d844d1a28efba81d5aca7385e24c29d3a6db2
> > > > Author: Sean Young <sean@mess.org>
> > > > Date:   Fri Sep 7 19:06:23 2012 +0100
> > > > 
> > > >     8250_pnp: do pnp probe before legacy probe
> > > > 
> > > > but that is simply moving code around.
> > > 
> > > Hi, not quite. Does it still happen when you revert that one on the top
> > > of 3.[789]*?
> > 
> > That was going to be my first attempt.  I'll let you know how it goes.
> 
> Yes, reverting just 835d844d1 on top of 3.7.0 fixes it.  I also see why
> now.  That commit changed the module name from 8250 to 8250_core in the
> makefile, so clearly 8250.nr_uarts = 16 isn't going to get parsed.
> Adding 8250_core.nr_uarts = 16 seems to work fine.  This wasn't
> immediately obvious because the whole thing is built-in and not a
> module.  Thankfully, looking in /sys/modules/ still works and that
> showed up pretty clearly.
> 
> So I guess this isn't really a break in functionality as much as it's a
> driver rename.  Not sure if it's worth fixing in some form or not.

Yes it needs to be fixed, we shouldn't break userspace stuff like that.
Patches gladly accepted.

thanks,

greg k-h

  reply	other threads:[~2013-03-07 23:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 18:56 8250.nr_uarts broken in 3.7 Josh Boyer
2013-03-07 18:58 ` Josh Boyer
2013-03-07 19:07 ` Jiri Slaby
2013-03-07 19:10   ` Josh Boyer
2013-03-07 21:14     ` Josh Boyer
2013-03-07 23:12       ` Greg Kroah-Hartman [this message]
2013-03-08  1:01         ` Josh Boyer
2013-03-08  1:39           ` Greg Kroah-Hartman
2013-03-08 21:27             ` Josh Boyer
2013-03-08 22:47               ` Jiri Slaby
2013-03-08 22:49                 ` Josh Boyer
2013-03-08 22:58                   ` Jiri Slaby
2013-03-08 23:10                     ` Jiri Slaby
2013-03-08 23:14                       ` Jiri Slaby
2013-03-08 23:28                         ` Josh Boyer
2013-03-08 23:44                           ` Josh Boyer
2013-03-09  9:14                             ` Jiri Slaby
2013-03-09 13:30                               ` Josh Boyer
2013-03-09 14:14                                 ` Jiri Slaby
2013-03-09 17:02                                   ` Josh Boyer
2013-03-10 14:33                                     ` [PATCH v2] serial: 8250: Keep 8250.<xxxx> module options functional after driver rename Josh Boyer
2013-03-10 22:33                                       ` Jiri Slaby
2013-03-10 12:21                                   ` 8250.nr_uarts broken in 3.7 Sean Young
2013-03-08 23:11                     ` Josh Boyer

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=20130307231242.GC4280@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=jwboyer@redhat.com \
    --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