linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] uio: ensure class is registered before devices
Date: Thu, 16 Aug 2018 12:04:13 +0200	[thread overview]
Message-ID: <20180816100413.GA9141@kroah.com> (raw)
In-Reply-To: <20180816083438.GE21707@piout.net>

On Thu, Aug 16, 2018 at 10:34:38AM +0200, Alexandre Belloni wrote:
> On 16/08/2018 10:01:12+0200, Greg Kroah-Hartman wrote:
> > On Thu, Aug 16, 2018 at 09:39:41AM +0200, Alexandre Belloni wrote:
> > > When both uio and the uio drivers are built in the kernel, it is possible
> > > for a driver to register devices before the uio class is registered.
> > 
> > How does this happen?  The link order should solve this issue, right?
> > 
> 
> Sure, if we can ensure uio_init() is called before any driver calls
> uio_register_device() then this would not happen. However, I'm not sure
> how you would want to achieve that.

That is the job of the link order, does this not work properly today?
How have you triggered this so that you could test your patch?

thanks,

greg k-h

  reply	other threads:[~2018-08-16 10:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16  7:39 [PATCH v2] uio: ensure class is registered before devices Alexandre Belloni
2018-08-16  8:01 ` Greg Kroah-Hartman
2018-08-16  8:34   ` Alexandre Belloni
2018-08-16 10:04     ` Greg Kroah-Hartman [this message]
2018-08-16 10:34       ` Alexandre Belloni
2018-08-16 10:44         ` Greg Kroah-Hartman

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=20180816100413.GA9141@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).