patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] kni: fix crash for KNI interface remove
Date: Mon, 26 Sep 2016 14:00:40 +0100	[thread overview]
Message-ID: <90a2b017-4c69-c94d-31ab-634e11b41aaf@intel.com> (raw)
In-Reply-To: <20160926125616.GE20278@yliu-dev.sh.intel.com>

<...>

>>> but with a simple glimpse, the
>>> build issue might still remain. Say, commit 109febfe58f9 ("net/igb: move
>>> PCI device IDs from EAL") will not be applied (as there is no fixline),
>>
>> 109febfe58f9 & 221fba3b987c are in fixes line of this patch.
> 
> Oh, I see. You were fixing an issue that introduced in v16.11, but not
> v16.07.

Right.

<..>
> 
> BTW, may I ask some helps from you? As I said in another email, I saw
> quite many bug fixing patches for KNI. Would you help to list few (if
> any) that need be picked for v16.07 release? I mean, some bug fixing
> patches that fix some bugs before v16.07 (inclusive).

Sure, I will share the list.

<...>

      reply	other threads:[~2016-09-26 13:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1472648786-32404-1-git-send-email-ferruh.yigit@intel.com>
     [not found] ` <6154238.UfqKImgbgb@xps13>
2016-09-26  8:34   ` Yuanhan Liu
2016-09-26  8:54     ` Yuanhan Liu
2016-09-26  9:21     ` Ferruh Yigit
2016-09-26 12:15       ` Yuanhan Liu
2016-09-26 12:26         ` Ferruh Yigit
2016-09-26 12:56           ` Yuanhan Liu
2016-09-26 13:00             ` Ferruh Yigit [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=90a2b017-4c69-c94d-31ab-634e11b41aaf@intel.com \
    --to=ferruh.yigit@intel.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).