From: Robin Jarry <robin.jarry@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] kni: avoid using lsb_release script
Date: Fri, 25 Nov 2016 12:28:30 +0100 [thread overview]
Message-ID: <20161125112830.GN32665@6wind.com> (raw)
In-Reply-To: <f88de78b-1963-cfb7-acdb-84bfb5fccac0@intel.com>
2016-11-25, Ferruh Yigit:
>What about:
>+-include /etc/lsb-release
Sure, that cannot hurt.
>s/DISTRIB_ID/DISTRIB_RELEASE
Oops last minute typo... I'll submit a v2 right away.
--
Robin
prev parent reply other threads:[~2016-11-25 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 9:52 Robin Jarry
2016-11-25 11:27 ` Ferruh Yigit
2016-11-25 11:28 ` Robin Jarry [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=20161125112830.GN32665@6wind.com \
--to=robin.jarry@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).