All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-i2c@vger.kernel.org, Ben Dooks <ben-linux@fluff.org>,
	linux-kernel@vger.kernel.org,
	Dirk Brandewie <dirk.brandewie@gmail.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	John Bonesio <bones@secretlab.ca>,
	Stephen Warren <SWarren@nvidia.com>
Subject: Re: [PATCH] i2c: Allow i2c_add_numbered_adapter() to assign a bus id.
Date: Wed, 6 Jul 2011 09:51:41 +0200	[thread overview]
Message-ID: <20110706095141.0daca2db@endymion.delvare> (raw)
In-Reply-To: <20110706063746.GA26611@ponder.secretlab.ca>

On Wed, 6 Jul 2011 00:37:46 -0600, Grant Likely wrote:
> Actually, now that I'm looking at things, I don't think there will be
> a conflict.  Go ahead and take it via your tree so that I don't make
> Linus' life harder than it needs to be.

OK, I've added the patch to my quilt series for the time being, so
it'll be in linux-next. Let me know if you change your mind before I
send it to Linus during the 3.1 merge window.

-- 
Jean Delvare

WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Dirk Brandewie
	<dirk.brandewie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Sebastian Andrzej Siewior
	<bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
	John Bonesio <bones-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>,
	Stephen Warren <SWarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] i2c: Allow i2c_add_numbered_adapter() to assign a bus id.
Date: Wed, 6 Jul 2011 09:51:41 +0200	[thread overview]
Message-ID: <20110706095141.0daca2db@endymion.delvare> (raw)
In-Reply-To: <20110706063746.GA26611-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>

On Wed, 6 Jul 2011 00:37:46 -0600, Grant Likely wrote:
> Actually, now that I'm looking at things, I don't think there will be
> a conflict.  Go ahead and take it via your tree so that I don't make
> Linus' life harder than it needs to be.

OK, I've added the patch to my quilt series for the time being, so
it'll be in linux-next. Let me know if you change your mind before I
send it to Linus during the 3.1 merge window.

-- 
Jean Delvare

  reply	other threads:[~2011-07-06  7:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 18:55 [PATCH] i2c: Allow i2c_add_numbered_adapter() to assign a bus id Grant Likely
2011-06-27 18:55 ` Grant Likely
2011-06-27 19:02 ` Grant Likely
2011-06-27 19:02   ` Grant Likely
2011-07-05  8:53   ` Jean Delvare
2011-07-05  8:53     ` Jean Delvare
2011-07-05 13:31     ` Grant Likely
2011-07-05 13:31       ` Grant Likely
2011-07-06  6:37     ` Grant Likely
2011-07-06  6:37       ` Grant Likely
2011-07-06  7:51       ` Jean Delvare [this message]
2011-07-06  7:51         ` Jean Delvare

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=20110706095141.0daca2db@endymion.delvare \
    --to=khali@linux-fr.org \
    --cc=SWarren@nvidia.com \
    --cc=ben-linux@fluff.org \
    --cc=bigeasy@linutronix.de \
    --cc=bones@secretlab.ca \
    --cc=dirk.brandewie@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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.