DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: Simon Kagstrom <simon.kagstrom@netinsight.net>,
	"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] kni: Use utsrelease.h to determine Ubuntu kernel version
Date: Wed, 4 Nov 2015 08:30:16 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A935143@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20150820085106.32188573@miho>



> -----Original Message-----
> From: Simon Kagstrom [mailto:simon.kagstrom@netinsight.net]
> Sent: Thursday, August 20, 2015 2:51 PM
> To: Zhang, Helin; thomas.monjalon@6wind.com; dev@dpdk.org
> Subject: [PATCH v2] kni: Use utsrelease.h to determine Ubuntu kernel version
> 
> /proc/version_signature is the version for the host machine, but in e.g., chroots,
> this does not necessarily match that DPDK is built for. DPDK will then build for the
> wrong kernel version - that of the server, and not that installed in the (build)
> chroot.
> 
> The patch uses utsrelease.h from the kernel sources instead and fakes the
> upload version.
> 
> Tested on a server with Ubuntu 12.04, building in a chroot for Ubuntu 14.04.
> 
> Signed-off-by: Simon Kagstrom <simon.kagstrom@netinsight.net>
> Signed-off-by: Johan Faltstrom <johan.faltstrom@netinsight.net>
Acked-by: Helin Zhang <helin.zhang@intel.com>

  parent reply	other threads:[~2015-11-04  8:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20  6:51 Simon Kagstrom
2015-10-13 12:50 ` Simon Kagstrom
2015-10-13 13:06   ` Tom Ghyselinck
2015-11-04  7:53 ` Simon Kågström
2015-11-04  8:30 ` Zhang, Helin [this message]
2015-11-19  9:08   ` Thomas Monjalon
2015-11-04 10:35 ` Thomas Monjalon
2015-11-04 11:29   ` Simon Kågström
2015-11-04 18:21     ` Stephen Hemminger
2015-11-05  8:20       ` Simon Kågström

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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A935143@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=simon.kagstrom@netinsight.net \
    --cc=thomas.monjalon@6wind.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).