DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Cc: dg@adax.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] kni: rename variable
Date: Tue, 14 Jan 2020 18:43:53 +0000	[thread overview]
Message-ID: <8a001359-bd84-fb5c-b268-6d59779001cf@intel.com> (raw)
In-Reply-To: <20191221010214.25735-1-stephen@networkplumber.org>

On 12/21/2019 1:02 AM, Stephen Hemminger wrote:
> All global variables in kernel should be prefixed by the same
> to avoid any symbol conflics. Rename dflt_carrier to kni_default_carrier.
> 
> Fixes: 89397a01ce4a ("kni: set default carrier state of interface")
> Cc: dg@adax.com
> Cc: stable@dpdk.org
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>

Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

  reply	other threads:[~2020-01-14 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-21  1:02 [dpdk-dev] " Stephen Hemminger
2020-01-14 18:43 ` Ferruh Yigit [this message]
2020-01-19 23:21   ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon

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=8a001359-bd84-fb5c-b268-6d59779001cf@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=dg@adax.com \
    --cc=stable@dpdk.org \
    --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;
as well as URLs for NNTP newsgroup(s).