public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Richard Palethorpe <rpalethorpe@suse.de>
To: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] getcpu01: Reinstate node_id test
Date: Tue, 13 Dec 2022 10:36:00 +0000	[thread overview]
Message-ID: <877cyvsi3l.fsf@suse.de> (raw)
In-Reply-To: <e0488665-e68e-455d-6ee6-8709b5f57599@fujitsu.com>

Hello,

>> 
>> FYI Richie is touching the same code, one of you will need to rebase.
>> IMHO it's better to remove this in dedicated patchset (i.e. in Xu).
>
> Even I will limit the kernel version check to 3.0 in my patchset because 
> we don't reach the same target to 3.10, so let me rebase.
>
> ps: If we reach the same target to 3.10, then we can remove remain old 
> version check in the future.

I'm not sure what you mean. It's not the important thing for this patch
though. I'll just remove it before merge.

>
> Best Regards
> Yang Xu
>> 
>> Kind regards,
>> Petr
>> 
>>> -static void setup(void)
>>> -{
>>> -	if (tst_kvercmp(2, 6, 20) < 0)
>>> -		tst_brk(TCONF, "kernel >= 2.6.20 required");
>>> -}
>>> -
>>>   static struct tst_test test = {
>>>   	.test_all = run,
>>> -	.setup = setup,
>>>   };


-- 
Thank you,
Richard.

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-12-13 10:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13  9:44 [LTP] [PATCH v2] getcpu01: Reinstate node_id test Richard Palethorpe via ltp
2022-12-13  9:53 ` Petr Vorel
2022-12-13 10:00   ` xuyang2018.jy
2022-12-13 10:36     ` Richard Palethorpe [this message]
2022-12-13 19:02       ` Petr Vorel

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=877cyvsi3l.fsf@suse.de \
    --to=rpalethorpe@suse.de \
    --cc=ltp@lists.linux.it \
    --cc=xuyang2018.jy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox