From: Daniel Silverstone <dsilvers-Y5A6D6n0/KfQXOPxS62xeg@public.gmane.org>
To: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: what is in bjdooks' i2c-for-2630 tree
Date: Fri, 27 Mar 2009 11:48:45 +0000 [thread overview]
Message-ID: <1238154525.25634.11.camel@petitemort> (raw)
In-Reply-To: <20090327110634.GJ19758-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
On Fri, 2009-03-27 at 11:06 +0000, Ben Dooks wrote:
> If anyone thinks there's more stuff that should be in here,
> let me know ASAP, will be pushing this to linus in the next
> day or so.
I take it there still hasn't been a decision about the renaming of the
platform_i2c structure? Or is it too late to get that kind of patch in
for 2.6.30 ?
Thanks,
Daniel.
--
Daniel Silverstone http://www.simtec.co.uk/
PGP mail accepted and encouraged. Key Id: 2BC8 4016 2068 7895
next prev parent reply other threads:[~2009-03-27 11:48 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 [this message]
2009-03-27 18:25 ` Mark Brown
[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=1238154525.25634.11.camel@petitemort \
--to=dsilvers-y5a6d6n0/kfqxopxs62xeg@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@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