From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] [PATCH lttng-modules 1/2] Fix: Allow alphanumeric characters in SLE version
Date: Thu, 9 Aug 2018 15:10:51 -0400 (EDT) [thread overview]
Message-ID: <476220740.474.1533841851513.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <20180809155532.7015-1-mjeanson@efficios.com>
Both merged into master, thanks!
Mathieu
----- On Aug 9, 2018, at 11:55 AM, Michael Jeanson mjeanson at efficios.com wrote:
> Allow alphanumeric characters in the long version string before
> extracting specific version numbers. This prevents failure in detecting
> a SuSE kernel when the version string was customized by the end user.
>
> Signed-off-by: Michael Jeanson <mjeanson at efficios.com>
> ---
> scripts/abi-sle-version.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/abi-sle-version.sh b/scripts/abi-sle-version.sh
> index bd6d5f1..aafed7c 100755
> --- a/scripts/abi-sle-version.sh
> +++ b/scripts/abi-sle-version.sh
> @@ -23,7 +23,7 @@ if [ ! -f "${KPATH}/include/generated/utsrelease.h" ]; then
> exit 0
> fi
>
> -SLE_RELEASE="$(sed -rn 's/^#define UTS_RELEASE "(.*)-([0-9\.]+)-(.*)"/\2/p'
> "${KPATH}/include/generated/utsrelease.h")"
> +SLE_RELEASE="$(sed -rn 's/^#define UTS_RELEASE
> "(.*)-([0-9a-zA-Z\.]+)-(.*)"/\2/p' "${KPATH}/include/generated/utsrelease.h")"
>
> SLE_RELEASE_MAJOR="$(echo "${SLE_RELEASE}" | sed -rn 's/^([0-9]+)(.*)$/\1/p')"
> SLE_RELEASE_MINOR="$(echo "${SLE_RELEASE}" | sed -rn
> 's/^([0-9]+)\.([0-9]+)(.*)$/\2/p')"
> --
> 2.17.1
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
prev parent reply other threads:[~2018-08-09 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 15:55 Michael Jeanson
2018-08-09 15:55 ` [lttng-dev] [PATCH lttng-modules 2/2] Fix: adjust SLE version ranges to build with SP2 and SP3 Michael Jeanson
2018-08-09 19:10 ` Mathieu Desnoyers [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=476220740.474.1533841851513.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.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