All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: bjdooks' i2c-next
Date: Wed, 12 May 2010 02:06:45 +0200	[thread overview]
Message-ID: <20100512000645.GA13984@pengutronix.de> (raw)
In-Reply-To: <20100511232039.GA32733-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>

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

On Wed, May 12, 2010 at 12:20:39AM +0100, Ben Dooks wrote:

> Here's the current contents of my i2c-next. All branches are
> on http://git.fluff.org/gitweb?p=bjdooks/linux.git;a=summary
> 
> Let me know if there is anything that has been missed.

Yes, my branch of old patches. Can also repost a patch series, whatever you
prefer:

The following changes since commit b57f95a38233a2e73b679bea4a5453a1cc2a1cc9:
  Linus Torvalds (1):
        Linux 2.6.34-rc7

are available in the git repository at:

  git://git.pengutronix.de/git/wsa/linux-2.6.git for-i2c

Uwe Kleine-König (2):
      i2c/pxa: remove unused macro
      MAINTAINERS: add i2c tree for embedded platforms

Wolfram Sang (5):
      i2c/pxa: only define 'blue_murder'-function if DEBUG is #defined
      i2c/mpc: drop NO_IRQ
      i2c/cpm: drop NO_IRQ
      i2c/ibm-iic: drop NO_IRQ
      i2c/highlander: remover superflous variable

 MAINTAINERS                         |    1 +
 drivers/i2c/busses/i2c-cpm.c        |    2 +-
 drivers/i2c/busses/i2c-highlander.c |    5 ++---
 drivers/i2c/busses/i2c-ibm_iic.c    |   14 +++++++-------
 drivers/i2c/busses/i2c-mpc.c        |    6 +++---
 drivers/i2c/busses/i2c-pxa.c        |   26 ++++++++++++++------------
 6 files changed, 28 insertions(+), 26 deletions(-)

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

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

  parent reply	other threads:[~2010-05-12  0:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11 23:20 bjdooks' i2c-next Ben Dooks
     [not found] ` <20100511232039.GA32733-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2010-05-12  0:06   ` Wolfram Sang [this message]
     [not found]     ` <20100512000645.GA13984-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-05-12  2:41       ` Ben Dooks
     [not found]         ` <20100512024117.GN2589-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2010-05-12  2:45           ` Wolfram Sang

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=20100512000645.GA13984@pengutronix.de \
    --to=w.sang-bicnvbalz9megne8c9+irq@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.