From: "Simon Kågström" <simon.kagstrom@netinsight.net>
To: "Wodkowski, PawelX" <pawelx.wodkowski@intel.com>,
"Zhang, Helin" <helin.zhang@intel.com>,
Alexander Guy <alexander@andern.org>,
Julien Cretin <julien.cretin@trust-in-soft.com>,
"Buriez, Patrice" <patrice.buriez@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] kni: Use utsrelease.h to determine Ubuntu kernel version
Date: Thu, 28 May 2015 14:12:21 +0200 [thread overview]
Message-ID: <55670625.5080805@netinsight.net> (raw)
In-Reply-To: <F6F2A6264E145F47A18AB6DF8E87425D1358F4CC@IRSMSX102.ger.corp.intel.com>
On 2015-05-28 12:48, Wodkowski, PawelX wrote:
>>> Please only check if UTS_RELEASE is available on all Ubuntu versions DPDK
>> support.
>>
>> From some digging, it appears it entered the kernel tree in 2006 and
>> moved to include/generated/ in 2009 so I guess that should be fine for
>> DPDK builds?
>
> I also think that it is OK but I also think should check by building you (o ask
> someone to do it for you) on those systems not by theory :)
Well, I think this is one of the main motivations from something like
what Thomas F. Herbert proposed in another thread recently,
DPDK: Proposal for a patch patch-test integration tree
basically, a continuous-integration-type of system should test-build
(and probably test) any prospective patch to see that it builds for
various targets. In my view, this would be a perfect match for
github+travis-ci.
Anyway, I'll see if I can dig up an older Ubuntu to build on, unless
someone else steps up and tests the patch. (My issue to start with was
that the build fails on a 14.04 chroot on a 12.04 host, but I only have
access to the chroot there).
// Simon
next prev parent reply other threads:[~2015-05-28 12:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 11:45 [PATCH] kni: Use utsrelease.h to determine Ubuntu kernel version Simon Kagstrom
2015-05-28 3:30 ` Zhang, Helin
2015-05-28 10:05 ` Wodkowski, PawelX
2015-05-28 10:37 ` Simon Kågström
2015-05-28 10:48 ` Wodkowski, PawelX
2015-05-28 11:06 ` Buriez, Patrice
2015-05-28 11:35 ` Wodkowski, PawelX
2015-05-28 12:12 ` Simon Kågström [this message]
2015-05-28 4:00 ` Stephen Hemminger
2015-06-16 21:09 ` Thomas Monjalon
2015-07-10 14:43 ` 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=55670625.5080805@netinsight.net \
--to=simon.kagstrom@netinsight.net \
--cc=alexander@andern.org \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=julien.cretin@trust-in-soft.com \
--cc=patrice.buriez@intel.com \
--cc=pawelx.wodkowski@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.