From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: Joseph Gasparakis <joseph.gasparakis@intel.com>,
netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com,
Don Skidmore <donald.c.skidmore@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [net-next 2/2] ixgbe: Get and display the notifications from changes of the Rx vxlan UDP port
Date: Tue, 27 Aug 2013 21:53:08 -0700 [thread overview]
Message-ID: <1377665588.2005.39.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1377665218-6760-2-git-send-email-jeffrey.t.kirsher@intel.com>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On Tue, 2013-08-27 at 21:46 -0700, Jeff Kirsher wrote:
> From: Joseph Gasparakis <joseph.gasparakis@intel.com>
>
> This RFC patch showcases how drivers can use the changes in
> "vxlan: Notify drivers for listening UDP port changes", and its
> sole purpose is to help people test the changes introduced there.
> This is not meant to be submitted for inclusion in the kernel.
>
> CC: Don Skidmore <donald.c.skidmore@intel.com>
> CC: Stephen Hemminger <stephen@networkplumber.org>
> Signed-off-by: Joseph Gasparakis <joseph.gasparakis@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 25
> +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
Just to be clear, this patch is an RFC. I missed putting it in the
patch title.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-28 4:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 4:46 [net-next 1/2] vxlan: Notify drivers for listening UDP port changes Jeff Kirsher
2013-08-28 4:46 ` [net-next 2/2] ixgbe: Get and display the notifications from changes of the Rx vxlan UDP port Jeff Kirsher
2013-08-28 4:53 ` Jeff Kirsher [this message]
2013-08-28 7:47 ` [net-next 1/2] vxlan: Notify drivers for listening UDP port changes Cong Wang
2013-08-28 11:43 ` Ben Hutchings
2013-08-28 19:34 ` John Fastabend
2013-08-28 20:41 ` Joseph Gasparakis
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=1377665588.2005.39.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=donald.c.skidmore@intel.com \
--cc=gospo@redhat.com \
--cc=joseph.gasparakis@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.com \
--cc=stephen@networkplumber.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