From: chrubis@suse.cz
To: Wanlong Gao <gaowanlong@cn.fujitsu.com>
Cc: LTP <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH V2 1/2] lib: let tst_kvercmp2() contains major kernel version
Date: Tue, 16 Jul 2013 15:24:25 +0200 [thread overview]
Message-ID: <20130716132425.GA21306@rei> (raw)
In-Reply-To: <51E540CC.3070406@cn.fujitsu.com>
Hi!
> Assume that we want version ">=2.6.25", but only ">2.6.18-131", contain
> them together will make no sense. I suppose only use tst_kvercmp2()
> "<0" and ">0", no use "=0", just remain return value "0" to indicate
> that the extra kernel vendor is not match with current kernel.
> What do you think?
Given that the kernel versions increase monotonically one can always
change that to:
> 2.6.24 && > 2.6.18-131
or (what I did in the example)
>= 2.6.25 && >= 2.6.18-132
Or am I missing something?
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-07-16 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1373966367-18078-1-git-send-email-gaowanlong@cn.fujitsu.com>
2013-07-16 11:43 ` [LTP] [PATCH V2 1/2] lib: let tst_kvercmp2() contains major kernel version chrubis
[not found] ` <51E540CC.3070406@cn.fujitsu.com>
2013-07-16 13:24 ` chrubis [this message]
[not found] ` <51E554C8.4070307@cn.fujitsu.com>
2013-07-16 15:52 ` chrubis
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=20130716132425.GA21306@rei \
--to=chrubis@suse.cz \
--cc=gaowanlong@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.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 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.