linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Ryan Mallon <ryan@bluewatersys.com>
Cc: Robert Emanuele <rob@emanuele.us>,
	Linus Walleij <linus.ml.walleij@gmail.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-i2c@vger.kernel.org
Subject: Re: Controlling Driver Load Order
Date: Fri, 28 May 2010 00:09:51 +0200	[thread overview]
Message-ID: <20100527220951.GD5636@pengutronix.de> (raw)
In-Reply-To: <4BFEEA08.70401@bluewatersys.com>

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

> > Always ask which kernel is used, sigh...
> 
> Sorry? I didn't see a kernel version mentioned. I went looking because I
> had though that i2c-gpio was already subsys_initcall.

Sorry, I missed emphasizing that my comment was meant as a "note-to-myself".
You were perfectly right, of course, I should have done the same.

> >> There was a discussion a while back to make all of the embedded i2c
> >> busses be subsys_initcall since i2c is often a system bus on embedded
> > 
> > Oh, where was that? Can't recall (but couldn't recall that I acked the i2c-gpio
> > patch above as well ;))
> > 
> 
> Moving the embedded i2c busses to subsys_initcall was discussed here:
> http://lists.lm-sensors.org/pipermail/i2c/2008-June/004142.html. The
> i2c_gpio bus got mentioned, which is why I thought it had already been
> changed.

Thanks for the pointer!

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2010-05-27 22:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 19:08 Controlling Driver Load Order Robert Emanuele
2010-05-26 21:04 ` Linus Walleij
2010-05-26 21:04   ` Linus Walleij
2010-05-26 23:52   ` Wolfram Sang
2010-05-27  1:33     ` Robert Emanuele
2010-05-27  1:39     ` Robert Emanuele
2010-05-27  4:13       ` Wolfram Sang
2010-05-27 17:07         ` Robert Emanuele
2010-05-27 21:01           ` Wolfram Sang
2010-05-27 21:09           ` Ryan Mallon
2010-05-27 21:42             ` Wolfram Sang
2010-05-27 21:54               ` Ryan Mallon
2010-05-27 22:09                 ` Wolfram Sang [this message]

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=20100527220951.GD5636@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=linus.ml.walleij@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@emanuele.us \
    --cc=ryan@bluewatersys.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;
as well as URLs for NNTP newsgroup(s).