From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rami Rosen <ramirose@gmail.com>, dev@dpdk.org
Cc: jingjing.wu@intel.com, wenzhuo.lu@intel.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH ] net/avf/base: fix comment referencing internal data
Date: Fri, 21 Dec 2018 14:10:27 +0000 [thread overview]
Message-ID: <d96c695e-c7af-bad1-1388-ef92189c54f9@intel.com> (raw)
In-Reply-To: <20181221121659.5214-1-ramirose@gmail.com>
On 12/21/2018 12:16 PM, Rami Rosen wrote:
> DCR is Intel internal information, no need to be in public code.
> See also a parallel patch by Ferruh, commit
> 1a0833efde70 ("net/i40e/base: fix comment referencing internal data").
>
> Fixes: e5b2a9e957e7 ("net/avf/base: add base code for avf PMD")
> Cc: stable@dpdk.org
>
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-12-21 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 12:16 [dpdk-dev] " Rami Rosen
2018-12-21 14:10 ` 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=d96c695e-c7af-bad1-1388-ef92189c54f9@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=ramirose@gmail.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@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).