patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "John Daley (johndale)" <johndale@cisco.com>
To: Harish Patil <harish.patil@qlogic.com>,
	Yuanhan Liu <yuanhan.liu@linux.intel.com>,
	dpdk stable <stable@dpdk.org>,
	"Mody, Rasesh" <Rasesh.Mody@cavium.com>
Cc: "Nelson Escobar (neescoba)" <neescoba@cisco.com>
Subject: Re: [dpdk-stable] request backporting some patches to 16.07.2
Date: Wed, 16 Nov 2016 22:01:51 +0000	[thread overview]
Message-ID: <38afa48eb21741509728401ee38e27fc@XCH-RCD-007.cisco.com> (raw)
In-Reply-To: <D451CE72.AEFB0%Harish.Patil@cavium.com>

Hi,
For Enic PMD, these 3 seem to already be in the stable branch, so no issues:
>> net/enic: document how to configure vNIC parameters 
> >net/enic: fix crash on MTU update or Rx queue reconfigure
> >net/enic: fix multi-queue Rx performance

For this one, I submitted another patch yesterday to stable@ which was rebased on top of the 16.07 stable branch and should apply clean:
> >net/enic: fix Rx queue index when not using Rx scatter

Other than that, enic is good (at least for now ;)

Thanks for managing the branch!

JohnD




  reply	other threads:[~2016-11-16 22:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-06  7:22 Yuanhan Liu
2016-11-15 13:58 ` Yuanhan Liu
2016-11-16 10:48   ` Maciej Czekaj
2016-11-16 11:57     ` Yuanhan Liu
2016-11-18 12:23   ` [dpdk-stable] [PATCH 1/2] kni: fix build with kernel 4.8 Ferruh Yigit
2016-11-18 12:23     ` [dpdk-stable] [PATCH 2/2] kni: fix build with kernel 4.9 Ferruh Yigit
2016-11-21  6:07     ` [dpdk-stable] [PATCH 1/2] kni: fix build with kernel 4.8 Yuanhan Liu
2016-11-16 16:51 ` [dpdk-stable] request backporting some patches to 16.07.2 Harish Patil
2016-11-16 22:01   ` John Daley (johndale) [this message]
2016-11-15 13:29 Yuanhan Liu
2016-11-21  9:38 ` Kusztal, ArkadiuszX
2016-11-21 11:31   ` Yuanhan Liu

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=38afa48eb21741509728401ee38e27fc@XCH-RCD-007.cisco.com \
    --to=johndale@cisco.com \
    --cc=Rasesh.Mody@cavium.com \
    --cc=harish.patil@qlogic.com \
    --cc=neescoba@cisco.com \
    --cc=stable@dpdk.org \
    --cc=yuanhan.liu@linux.intel.com \
    /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).