From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Helin Zhang <helin.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/3] kni: fix compile error for Linux 4.7
Date: Tue, 07 Jun 2016 11:22:32 +0200 [thread overview]
Message-ID: <1552892.9ntgPhfpuM@xps13> (raw)
In-Reply-To: <1464607354-22728-1-git-send-email-ferruh.yigit@intel.com>
2016-05-30 12:22, Ferruh Yigit:
> Fix compile error becuase of Linux API change, 'trans_start' field
> removed from 'struct net_device'.
>
> Linux: 9b36627acecd ("net: remove dev->trans_start")
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Series applied, thanks
prev parent reply other threads:[~2016-06-07 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 11:22 Ferruh Yigit
2016-05-30 11:22 ` [dpdk-dev] [PATCH 2/3] kni: compat.h syntax update Ferruh Yigit
2016-05-30 11:22 ` [dpdk-dev] [PATCH 3/3] kni: move more kernel version check to compat header Ferruh Yigit
2016-06-07 9:22 ` Thomas Monjalon [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=1552892.9ntgPhfpuM@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=helin.zhang@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).