From: Mark Brown <broonie-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
To: Ben Dooks <ben-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dsilvers-Y5A6D6n0/KfQXOPxS62xeg@public.gmane.org
Subject: Re: what is in bjdooks' i2c-for-2630 tree
Date: Fri, 27 Mar 2009 18:25:22 +0000 [thread overview]
Message-ID: <20090327182522.GA13372@sirena.org.uk> (raw)
In-Reply-To: <E1Ln9pC-00037e-Qn-fIsYBodh/r28n8r38hOLvmD2FQJk+8+b@public.gmane.org>
On Fri, Mar 27, 2009 at 11:02:10AM +0000, Ben Dooks wrote:
> The following changes since commit 8e0ee43bc2c3e19db56a4adaa9a9b04ce885cd84:
> Linus Torvalds (1):
> Linux 2.6.29
> are available in the git repository at:
> git://aeryn.fluff.org.uk/bjdooks/linux.git i2c-for-2630
There was also a change I posted a while ago to initialise the S3C I2C
driver earlier in order to allow I2C devices to be used earlier in init
- this is useful for things like regulators which are expected to be
configured very early on. Were there any problems with it?
next prev parent reply other threads:[~2009-03-27 18:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 11:02 what is in bjdooks' i2c-for-2630 tree Ben Dooks
[not found] ` <E1Ln9pC-00037e-Qn-fIsYBodh/r28n8r38hOLvmD2FQJk+8+b@public.gmane.org>
2009-03-27 11:06 ` Ben Dooks
[not found] ` <20090327110634.GJ19758-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2009-03-27 11:48 ` Daniel Silverstone
2009-03-27 18:25 ` Mark Brown [this message]
[not found] ` <20090327182522.GA13372-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2009-03-27 22:33 ` Ben Dooks
2009-03-30 0:28 ` Ben Dooks
-- strict thread matches above, loose matches on Subject: below --
2009-03-27 10:56 Ben Dooks
[not found] ` <E1Ln9js-00030o-8s-fIsYBodh/r28n8r38hOLvmD2FQJk+8+b@public.gmane.org>
2009-03-27 11:03 ` Ben Dooks
[not found] ` <20090327110331.GH19758-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2009-03-27 11:05 ` Ben Dooks
2009-03-27 10:56 Ben Dooks
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=20090327182522.GA13372@sirena.org.uk \
--to=broonie-gfdadszt00ze9xe1eozjha@public.gmane.org \
--cc=ben-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org \
--cc=dsilvers-Y5A6D6n0/KfQXOPxS62xeg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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