patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Harish Patil <harish.patil@qlogic.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	Dept-Eng DPDK Dev <Dept-EngDPDKDev@cavium.com>
Subject: Re: [dpdk-stable] [PATCH 1/3] net/qede: fix missing UDP protocol in RSS offload types
Date: Tue, 28 Mar 2017 21:20:34 +0000	[thread overview]
Message-ID: <BLUPR0701MB157233BBED10A8DF9D33205D9F320@BLUPR0701MB1572.namprd07.prod.outlook.com> (raw)
In-Reply-To: <f5373868-128e-9c03-cae6-478c7961b8a6@intel.com>

> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
> Sent: Tuesday, March 28, 2017 5:19 AM
> 
> On 3/24/2017 7:40 AM, Rasesh Mody wrote:
> > From: Harish Patil <harish.patil@qlogic.com>
> >
> > Both UDP and TCP based RSS offload types are supported by the device.
> > This patch adds UDP protocol which got missed out in the original patch.
> >
> > Fixes: 4c98f2768eef ("net/qede: support RSS hash configuration")
> >
> > Signed-off-by: Harish Patil <harish.patil@qlogic.com>
> 
> This patchset looks like depends to other patchset, can you please confirm?

Yes, this patch set does depend on the v4 patchset.

Thanks!
-Rasesh

  reply	other threads:[~2017-03-28 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24  7:40 Rasesh Mody
2017-03-24  7:40 ` [dpdk-stable] [PATCH 2/3] net/qede: fix VF's RSS configuration failure Rasesh Mody
2017-03-24  7:40 ` [dpdk-stable] [PATCH 3/3] net/qede: prevent crash while changing MTU dynamically Rasesh Mody
2017-03-28 12:18 ` [dpdk-stable] [PATCH 1/3] net/qede: fix missing UDP protocol in RSS offload types Ferruh Yigit
2017-03-28 21:20   ` Mody, Rasesh [this message]
2017-03-30 14:27 ` Ferruh Yigit

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=BLUPR0701MB157233BBED10A8DF9D33205D9F320@BLUPR0701MB1572.namprd07.prod.outlook.com \
    --to=rasesh.mody@cavium.com \
    --cc=Dept-EngDPDKDev@cavium.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=harish.patil@qlogic.com \
    --cc=stable@dpdk.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).