linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <mike-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
To: Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: current -next tree from bjdooks
Date: Sun, 09 Jan 2011 08:58:22 +0200	[thread overview]
Message-ID: <4D295C8E.8010509@compulab.co.il> (raw)
In-Reply-To: <20110104013005.GE817-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>

Hi Ben,

Can you please add the "i2c-mv64xxx: use subsys_initcall for early
initialization" patch (1) to the queue?

[1] http://www.spinics.net/lists/linux-i2c/msg03816.html

On 01/04/11 03:30, Ben Dooks wrote:
> Updated my next tree, and published it. I've included a pull-request
> as an overview. Please review and re-post anything that either was
> asked to be reviewed and has been sorted, or items that are missing.
> 
> The following changes since commit 03ed6a3aa600c48593c3984812fda2d5945ddb46:
> 
>   Merge branch 'perf-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip (2011-01-03 11:51:22 -0800)
> 
> are available in the git repository at:
> 
>   git://git.fluff.org/bjdooks/linux.git next-i2c
> 
> Aaro Koskinen (1):
>       i2c-iop3xx: add iomem annotation
> 
> Ben Dooks (5):
>       Merge branch 'for-2638/i2c/iop' into next-i2c
>       Merge branch 'for-2638/i2c/mv64xx' into next-i2c
>       Merge branch 'for-2638/i2c/nomadik' into next-i2c
>       Merge branch 'for-2638/i2c/ocores' into next-i2c
>       Merge branch 'for-2638/i2c/omap' into next-i2c
> 
> Jonas Bonn (3):
>       i2c-ocores: Adapt for device tree
>       i2c-ocores: Use devres for resource allocation
>       i2c-ocores: add some device tree documentation
> 
> Linus Walleij (1):
>       i2c-nomadik: fix regression on adapter name
> 
> Rodolfo Giometti (1):
>       i2c-mv64xxx: send repeated START between messages in xfer
> 
> Samu Onkalo (1):
>       i2c-omap: Set latency requirements only once for several messages
> 
> Tomoya MORINAGA (1):
>       i2c-eg20t: add driver for Intel EG20T
> 
>  drivers/i2c/busses/Kconfig       |    8 +
>  drivers/i2c/busses/Makefile      |    1 +
>  drivers/i2c/busses/i2c-eg20t.c   |  900 ++++++++++++++++++++++++++++++++++++++
>  drivers/i2c/busses/i2c-iop3xx.c  |    6 +-
>  drivers/i2c/busses/i2c-iop3xx.h  |    2 +-
>  drivers/i2c/busses/i2c-mv64xxx.c |   45 ++-
>  drivers/i2c/busses/i2c-nomadik.c |    6 +-
>  drivers/i2c/busses/i2c-ocores.c  |  145 +++++--
>  drivers/i2c/busses/i2c-omap.c    |   10 +-
>  9 files changed, 1063 insertions(+), 60 deletions(-)
>  create mode 100644 drivers/i2c/busses/i2c-eg20t.c
> 


-- 
Sincerely yours,
Mike.

      parent reply	other threads:[~2011-01-09  6:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04  1:30 current -next tree from bjdooks Ben Dooks
     [not found] ` <20110104013005.GE817-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2011-01-09  6:58   ` Mike Rapoport [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=4D295C8E.8010509@compulab.co.il \
    --to=mike-utxizqzc01rs1mouv/rt9w@public.gmane.org \
    --cc=ben-i2c-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;
as well as URLs for NNTP newsgroup(s).