From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Xiao Wang <xiao.w.wang@intel.com>, jing.d.chen@intel.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] net/fm10k: fix pointer cast
Date: Wed, 29 Mar 2017 12:20:05 +0100 [thread overview]
Message-ID: <2de9b5ec-881b-a028-8113-dc2d1bcc60b9@intel.com> (raw)
In-Reply-To: <73b82694-0245-0177-160a-a6717644fa9f@intel.com>
On 3/29/2017 12:18 PM, Ferruh Yigit wrote:
> On 3/28/2017 4:57 AM, Xiao Wang wrote:
>> The device specific data is located at dev->data->dev_private.
>>
>> Fixes: 162f32290a99 ("fm10k: move parameters initialization")
>> Fixes: 039991bc28ff ("fm10k: add vector pre-condition check")
>> Fixes: 77a8ab47eb38 ("fm10k: select best Rx function")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-03-29 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 3:57 Xiao Wang
2017-03-29 11:18 ` Ferruh Yigit
2017-03-29 11:20 ` 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=2de9b5ec-881b-a028-8113-dc2d1bcc60b9@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jing.d.chen@intel.com \
--cc=stable@dpdk.org \
--cc=xiao.w.wang@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).