linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: torvalds@linux-foundation.org
Cc: akpm@linux-foundation.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT] IDE
Date: Fri, 17 Sep 2010 21:19:46 -0700 (PDT)	[thread overview]
Message-ID: <20100917.211946.38301858.davem@davemloft.net> (raw)


Thanks to the excellent detective work and patch written by
Wolfram Sang, we have a fix for along standing issue in IDE.

The procfs directory for devices underneath an IDE controller
instance is not created before we try to makes nodes in that
directory.

The problem doesn't happen if, for example, you build everything
IDE statically into your kernel.  This is because the individual
host controller drivers initialize first and probe the IDE
controllers.  But the CDROM, disk, et al. driver's haven't
setup yet.  They do so later, and at that point is when the
nodes in the procfs directory get created.  And this works in
this case because the procfs directory is setup by the time
those device type drivers initialize.

But if we register an IDE controller device after the CDROM,
disk, et al. IDE modules have setup, we hit the problem.

Please pull, thanks a lot!

The following changes since commit 03a7ab083e4d619136d6f07ce70fa9de0bc436fc:

  Merge git://git.kernel.org/pub/scm/linux/kernel/git/sfrench/cifs-2.6 (2010-09-16 12:59:11 -0700)

are available in the git repository at:

  master.kernel.org:/pub/scm/linux/kernel/git/davem/ide-2.6.git master

Wolfram Sang (1):
      ide: Fix ordering of procfs registry.

 drivers/ide/ide-probe.c |   12 +++---------
 1 files changed, 3 insertions(+), 9 deletions(-)

             reply	other threads:[~2010-09-18  4:19 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-18  4:19 David Miller [this message]
2010-09-18 12:01 ` [GIT] IDE Wolfram Sang
  -- strict thread matches above, loose matches on Subject: below --
2020-04-06 18:24 David Miller
2020-04-07 19:55 ` pr-tracker-bot
2020-01-30 10:07 David Miller
2020-01-30 18:00 ` pr-tracker-bot
2019-07-13  6:17 [GIT] Ide David Miller
2019-07-13 23:15 ` pr-tracker-bot
2019-05-08 23:53 [GIT] IDE David Miller
2019-05-09  4:45 ` pr-tracker-bot
     [not found] ` <CGME20190510172236eucas1p138115389e72802f72e47158df6ed9871@eucas1p1.samsung.com>
2019-05-10 17:22   ` Bartlomiej Zolnierkiewicz
2019-03-11  5:00 David Miller
2019-03-11 17:50 ` pr-tracker-bot
2018-12-03  6:31 David Miller
2018-12-03 17:55 ` pr-tracker-bot
2018-08-22  5:17 David Miller
2018-06-09 14:20 David Miller
2018-02-01 15:32 David Miller
2017-11-19 12:43 David Miller
2017-07-21  3:40 David Miller
2017-05-09 20:04 David Miller
2017-02-28  1:50 David Miller
2016-07-29 17:57 David Miller
2016-03-28 19:45 David Miller
     [not found] <20160118.143241.1114572935099360375.davem@davemloft.net>
2016-01-18 19:33 ` David Miller
2015-11-03 21:44 David Miller
2015-04-17 20:14 David Miller
2015-03-19  4:59 David Miller
2014-12-12 21:00 David Miller
2014-10-15 18:44 David Miller
2014-08-06  5:03 David Miller
2014-07-22  5:37 David Miller
2014-01-29  8:50 David Miller
2013-11-14 23:29 David Miller
2013-09-05 20:44 David Miller
2013-07-10 19:21 David Miller
2012-06-15 22:42 David Miller
2011-11-18 19:47 David Miller
2011-10-03 19:35 David Miller
2011-06-12  5:32 David Miller
2011-05-23  4:58 David Miller
2010-10-29  3:45 David Miller
2010-08-09 10:28 David Miller
2010-05-24  7:11 David Miller
2010-04-08  8:36 David Miller
2010-04-08 15:02 ` Linus Torvalds
2010-04-08 18:15   ` David Miller
2010-03-28  2:29 [GIT]: IDE David Miller
2010-03-29  2:01 ` David Miller
2010-03-04  8:25 David Miller
2009-12-08 23:49 David Miller
2009-11-30  9:17 David Miller
2009-11-09  5:30 David Miller
2009-11-09 10:35 ` Bartlomiej Zolnierkiewicz
2009-10-29 14:36 David Miller
2009-10-07 11:10 David Miller
2009-10-05 21:05 David Miller
2009-09-15  8:53 David Miller
2009-09-06 21:13 David Miller
2009-07-22  4:21 David Miller
2009-07-06 21:51 David Miller

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=20100917.211946.38301858.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).