DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wodkowski, PawelX" <pawelx.wodkowski@intel.com>
To: "Buriez, Patrice" <patrice.buriez@intel.com>,
	"Simon Kågström" <simon.kagstrom@netinsight.net>,
	"Zhang, Helin" <helin.zhang@intel.com>,
	"Alexander Guy" <alexander@andern.org>,
	"Julien Cretin" <julien.cretin@trust-in-soft.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] kni: Use utsrelease.h to determine Ubuntu kernel version
Date: Thu, 28 May 2015 11:35:33 +0000	[thread overview]
Message-ID: <F6F2A6264E145F47A18AB6DF8E87425D1358F561@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <8BBE948C60307D47AD16B5B5B92A387E32EDAC07@IRSMSX106.ger.corp.intel.com>



> -----Original Message-----
> From: Buriez, Patrice
> Sent: Thursday, May 28, 2015 1:07 PM
> To: Wodkowski, PawelX; Simon Kågström; Zhang, Helin; Alexander Guy; Julien
> Cretin
> Cc: dev@dpdk.org
> Subject: RE: [PATCH] kni: Use utsrelease.h to determine Ubuntu kernel version
> 
> Hi all,
> Please forgive top reply and bottom disclaimer.
> Not sure anyway that this email will reach the mailing list, since I did not
> subscribe to it.
> 
> I am worried about the removal of: cut -d'~' -f1
> It was introduced by Pawel in commit

You are absolutely right. That is why I asked to check with documentation
and to verify  with real build on all supported Ubuntu versions. :)


-- 
Pawel

  reply	other threads:[~2015-05-28 11:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 11:45 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 [this message]
2015-05-28 12:12         ` Simon Kågström
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=F6F2A6264E145F47A18AB6DF8E87425D1358F561@IRSMSX102.ger.corp.intel.com \
    --to=pawelx.wodkowski@intel.com \
    --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=simon.kagstrom@netinsight.net \
    /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).