mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux I2C <linux-i2c@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] i2c updates for 2.6.38
Date: Tue, 11 Jan 2011 12:25:00 +0100	[thread overview]
Message-ID: <20110111122500.203c4ce4@endymion.delvare> (raw)
In-Reply-To: <20110111111758.GH6541@sirena.org.uk>

Hi Mark,

On Tue, 11 Jan 2011 11:17:58 +0000, Mark Brown wrote:
> On Mon, Jan 10, 2011 at 10:21:45PM +0100, Jean Delvare wrote:
> > Hi Linus,
> > 
> > Please pull i2c subsystem updates for Linux 2.6.37 from:
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git i2c-for-linus
> > 
> > Not much this time around... Only the new generic I2C multiplexer using
> > the GPIO API is worth mentioning.
> 
> It'd be good to also get the conversion to use the pm_generic_ stuff in
> - that ends up fixing some bugs with the interaction between runtime and
> system suspend and at least means that it's no longer the responsibility
> of the I2C code to sort them out in future.  Linus merged the PM tree
> bits for that already.

Thanks for the reminder, I'll look into that as soon as possible and
when the patches are ready, I'll send another pull request to Linus.

-- 
Jean Delvare

  reply	other threads:[~2011-01-11 11:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 21:21 Jean Delvare
2011-01-10 22:32 ` Jean Delvare
2011-01-10 22:58   ` Randy Dunlap
2011-01-11 11:17 ` Mark Brown
2011-01-11 11:25   ` Jean Delvare [this message]
2011-01-11 11:24     ` Mark Brown
2011-01-13 21:22       ` Jean Delvare
2011-01-13 23:24         ` Mark Brown

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=20110111122500.203c4ce4@endymion.delvare \
    --to=khali@linux-fr.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®