From 15c93f417f8dd87f1655448b7c4c59e3fb8b5aba Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Tue, 8 Jun 2010 09:51:41 -0700 Subject: [PATCH] PORTING: Fix some typos. Reported-by: Justin Pettit --- PORTING | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/PORTING b/PORTING index 516da8905..c9c536938 100644 --- a/PORTING +++ b/PORTING @@ -127,10 +127,10 @@ There are two existing dpif implementations that may serve as useful examples during a port: * lib/dpif-linux.c is a Linux-specific dpif implementation that - talks to a Open vSwitch-specific kernel module (whose sources + talks to an Open vSwitch-specific kernel module (whose sources are in the "datapath" directory). The kernel module performs all of the switching work, passing packets that do not match any - flow table entry down to userspace. This dpif implementation is + flow table entry up to userspace. This dpif implementation is essentially a wrapper around calls to "ioctl". * lib/dpif-netdev.c is a generic dpif implementation that performs -- 2.43.0