netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Simon Horman <horms@verge.net.au>
Cc: netdev@vger.kernel.org, Jesse Gross <jesse@nicira.com>,
	Stephen Hemminger <shemminger@linux-foundation.org>,
	Chris Wright <chrisw@sous-sol.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Arnd Bergmann <arnd@arndb.de>, David Miller <davem@davemloft.net>
Subject: Re: [rfc] Merging the Open vSwitch datapath
Date: Mon, 30 Aug 2010 00:25:18 -0700	[thread overview]
Message-ID: <1283153118.7762.83.camel@Joe-Laptop> (raw)
In-Reply-To: <20100830071147.GB22396@verge.net.au>

On Mon, 2010-08-30 at 16:11 +0900, Simon Horman wrote:
> On Sun, Aug 29, 2010 at 11:52:05PM -0700, Joe Perches wrote:
> > On Mon, 2010-08-30 at 15:27 +0900, Simon Horman wrote:
> > > I am looking to submit the Open vSwitch datapath for merging into the
> > > kernel.  To this end I have posted a preliminary round of patches to the
> > > dev@openvswitch.org mailing list
> > > 2) The code could do with some cleaning up. The current todo list
> > >    includes the following items.
> > >    * Use pr_*
> > >    * Remove trailing whitespace and other formatting fixes
> > These are trivial and easy to fix via script.
> > I think these should be done prior to being merged.
> > I've got patches if you want them.
> Yes, please send them.

I've send them to you and cc'd the dev@openvswitch.org mailing list.


  reply	other threads:[~2010-08-30  7:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30  6:27 [rfc] Merging the Open vSwitch datapath Simon Horman
2010-08-30  6:52 ` Joe Perches
2010-08-30  7:11   ` Simon Horman
2010-08-30  7:25     ` Joe Perches [this message]
2010-08-30  7:33       ` Simon Horman
2010-08-30 17:22 ` Ben Pfaff
2010-08-30 18:26   ` Rose, Gregory V
2010-08-30 18:33     ` Ben Pfaff
2010-08-30 18:45       ` Rose, Gregory V
2010-08-30 20:59         ` Chris Wright
2010-08-31  0:48           ` Simon Horman
2010-08-31  0:54             ` Chris Wright
2010-08-31  1:01               ` Simon Horman
2010-08-31  1:11                 ` Jesse Gross
2010-08-31  1:38                   ` Simon Horman
2010-08-31  8:18               ` Herbert Xu
2010-08-30 21:04         ` Arnd Bergmann
2010-08-30 22:15           ` Rose, Gregory V
2010-08-31 11:48             ` Arnd Bergmann
2010-08-31 17:04               ` Rose, Gregory V
2010-08-31 17:43                 ` Arnd Bergmann
2010-08-31 20:16                   ` Rose, Gregory V
2010-10-15 11:31   ` openvswitch/flow WAS ( " jamal
2010-10-15 16:18     ` Ben Pfaff
2010-10-15 21:35     ` Jesse Gross
2010-10-16 11:35       ` jamal
2010-10-16 19:33         ` Jesse Gross
2010-10-18 12:16           ` jamal
2010-10-18 15:20             ` Simon Horman
2010-10-19 10:22               ` jamal
2010-10-19 14:56                 ` Simon Horman

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=1283153118.7762.83.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=arnd@arndb.de \
    --cc=chrisw@sous-sol.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=horms@verge.net.au \
    --cc=jesse@nicira.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@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;
as well as URLs for NNTP newsgroup(s).