From: Stephen Hemminger <shemminger@vyatta.com>
To: "Jeff Kirsher" <jeffrey.t.kirsher@intel.com>
Cc: netdev@vger.kernel.org,
"Alexander Duyck" <alexander.h.duyck@intel.com>,
"Jeff Kirsher" <jeffrey.t.kirsher@intel.com>,
davem@davemloft.net
Subject: Re: [PATCH 1/2] IPROUTE: add support for skbedit action
Date: Tue, 6 Jan 2009 19:30:18 -0800 [thread overview]
Message-ID: <20090106193018.1ccb2cd3@extreme> (raw)
In-Reply-To: <9929d2390812120231u20161604jd0abf90478112439@mail.gmail.com>
Applied. I am putting together iproute for 2.6.28 asap
prev parent reply other threads:[~2009-01-07 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 22:16 [PATCH 1/2] IPROUTE: add support for skbedit action Jeff Kirsher
2008-12-05 22:16 ` [PATCH 2/2] IPROUTE: add support for multiq qdisc Jeff Kirsher
2008-12-12 10:31 ` [PATCH 1/2] IPROUTE: add support for skbedit action Jeff Kirsher
2008-12-12 18:44 ` Stephen Hemminger
2009-01-07 3:30 ` Stephen Hemminger [this message]
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=20090106193018.1ccb2cd3@extreme \
--to=shemminger@vyatta.com \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@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 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).