All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: khali@linux-fr.org
Cc: sfr@canb.auug.org.au, bhutchings@solarflare.com,
	netdev@vger.kernel.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org, mika.kuoppala@nokia.com,
	linux-i2c@vger.kernel.org
Subject: Re: Shared i2c adapter locking
Date: Tue, 17 Nov 2009 03:51:47 -0800 (PST)	[thread overview]
Message-ID: <20091117.035147.80164577.davem@davemloft.net> (raw)
In-Reply-To: <20091117103554.03971b2f@hyperion.delvare>

From: Jean Delvare <khali@linux-fr.org>
Date: Tue, 17 Nov 2009 10:35:54 +0100

> If you did and something is still not clear, please let me know. My
> understanding is that the action token is in David's hands now.

So what exactly do I need to do?

All I see that needs to happen is to pull from Linus's tree into
net-2.6

But frankly I don't see how that helps resolve anything in linux-next
since Stephen starts with Linus's tree then pulls in everyone's work.

Or is that pull necessary so that some other patch can be applied
to net-2.6 or similar?

  reply	other threads:[~2009-11-17 11:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26  2:37 linux-next: manual merge of the net tree with the i2c tree Stephen Rothwell
2009-10-26  2:37 ` Stephen Rothwell
2009-10-26 13:46 ` Ben Hutchings
2009-10-29 14:43 ` Shared i2c adapter locking (Was: linux-next: manual merge of the net tree with the i2c tree) Jean Delvare
2009-10-29 14:43   ` Jean Delvare
2009-10-29 15:09   ` Ben Hutchings
2009-11-05 13:11     ` Shared i2c adapter locking Jean Delvare
2009-11-05 13:11       ` Jean Delvare
2009-11-05 13:57       ` Ben Hutchings
     [not found]         ` <1257429444.2793.2.camel-xQnnTUlwzDrdvaEqJLTMTA9jg9n5Vt1AMm0uRHvK7Nw@public.gmane.org>
2009-11-05 14:07           ` Jean Delvare
2009-11-05 14:07             ` Jean Delvare
2009-11-17  8:33             ` Stephen Rothwell
     [not found]               ` <20091117193313.b750804e.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-11-17  9:35                 ` Jean Delvare
2009-11-17  9:35                   ` Jean Delvare
2009-11-17 11:51                   ` David Miller [this message]
2009-11-17 13:32                     ` Ben Hutchings
2009-11-17 14:13                       ` David Miller
     [not found]                   ` <20091117103554.03971b2f-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-11-17 20:59                     ` Stephen Rothwell
2009-11-17 20:59                       ` Stephen Rothwell
     [not found]                       ` <20091118075917.9ac0248c.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-11-19  6:53                         ` David Miller
2009-11-19  6:53                           ` David Miller
2009-11-19  7:05                           ` Stephen Rothwell
2009-11-10 11:42 ` linux-next: manual merge of the net tree with the i2c tree Jean Delvare
2009-11-10 11:42   ` Jean Delvare
2009-11-10 13:22   ` Ben Hutchings
2009-11-10 15:02     ` Jean Delvare
2009-11-10 15:10       ` Ben Hutchings

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=20091117.035147.80164577.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bhutchings@solarflare.com \
    --cc=khali@linux-fr.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mika.kuoppala@nokia.com \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.