From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] tst_ncpus_conf: Instead of the old tst_ncpus_max
Date: Wed, 10 Sep 2014 14:45:25 +0800 [thread overview]
Message-ID: <540FF385.1050903@cn.fujitsu.com> (raw)
In-Reply-To: <1984956924.20366068.1410331044710.JavaMail.zimbra@redhat.com>
On 09/10/2014 02:37 PM, Jan Stancek wrote:
>
> ----- Original Message -----
>> > From: "Zeng Linggang" <zenglg.jy@cn.fujitsu.com>
>> > To: "ltp-list" <ltp-list@lists.sourceforge.net>
>> > Sent: Wednesday, 10 September, 2014 7:25:57 AM
>> > Subject: [LTP] [PATCH] tst_ncpus_conf: Instead of the old tst_ncpus_max
>> >
>> > In commit 84d608326c59b7177c8ad4228fbcd21569b4f2fd we have updated
>> > tst_ncpus_max
>> > function. But smt_smp_enabled.sh and smt_smp_affinity.sh need the old
>> > tst_ncpus_max, otherwise they will fail. Use tst_ncpus_conf instead of the
>> > old
>> > tst_ncpus_max function.
>> >
>> > Signed-off-by: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
> Looks good to me, ACK.
>
Applied, thank you.
Wanlong Gao
> Regards,
> Jan
>
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-09-10 6:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 5:25 [LTP] [PATCH] tst_ncpus_conf: Instead of the old tst_ncpus_max Zeng Linggang
2014-09-10 6:37 ` Jan Stancek
2014-09-10 6:45 ` Wanlong Gao [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=540FF385.1050903@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=zenglg.jy@cn.fujitsu.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.