patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/bnxt: fix a segfault encountered during PMD exit
Date: Wed, 16 Nov 2016 22:27:28 +0800	[thread overview]
Message-ID: <20161116142728.GJ5048@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <CACZ4nhuF_HxLtzJ8j7Uq+jobHBbAHGBPc88qDOZFS1KW0AHXrQ@mail.gmail.com>

On Tue, Nov 15, 2016 at 11:26:41PM -0600, Ajit Khaparde wrote:
> 
> 
> On Tue, Nov 15, 2016 at 8:19 PM, Yuanhan Liu <yuanhan.liu@linux.intel.com>
> wrote:
> 
>     Hi Ajit,
> 
>     Thanks for the backport. Few minor comments though:
> 
>     - the dev mailing list should not be cc'ed (thus I removed it).
> 
>     - the commit log should not be changed, except an extra line is needed:
> 
>       [ backported from upstream commit 316e412299fde9f8f099ef957aa04d
>     c6c43d02a2 ]
> 
> ​I had cloned the dpdk-stable for the first time. So it did not have the usual
> git hooks.
> By the time I got the email about the checkpatch failure, it was late anyway.
> ​
>  
> 
> 
>     You could either send another veresion, or I will handle it (copy &
>     ​​
>     paste the original commit log) for you while apply.
> 
> ​If it isn't much, could you just use this version and do the copy-paste this
> time.
> ​Otherwise I will send something out tomorrow. My laptop battery is almost out
> of power.

No worry, I could do it for you.

	--yliu

  reply	other threads:[~2016-11-16 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 23:06 [dpdk-stable] " Ajit Khaparde
2016-11-16  2:19 ` [dpdk-stable] [dpdk-dev] " Yuanhan Liu
2016-11-16  5:26   ` Ajit Khaparde
2016-11-16 14:27     ` Yuanhan Liu [this message]
2016-11-17 12:11       ` 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=20161116142728.GJ5048@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=ajit.khaparde@broadcom.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).