linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp@lists.linux.it, Ofer Levi <oferle@nvidia.com>,
	Rich Felker <dalias@libc.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-sh@vger.kernel.org, Vineet Gupta <vgupta@synopsys.com>,
	linux-mips@vger.kernel.org, linux-csky@vger.kernel.org,
	linux-m68k@lists.linux-m68k.org, Guo Ren <guoren@kernel.org>,
	Greentime Hu <green.hu@gmail.com>,
	"Maciej W . Rozycki" <macro@linux-mips.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Vincent Chen <deanbo422@gmail.com>
Subject: Re: [LTP] [PATCH 1/1] cacheflush01: Rewrite into new API
Date: Thu, 8 Oct 2020 22:04:06 +0200	[thread overview]
Message-ID: <20201008200406.GA18136@dell5510> (raw)
In-Reply-To: <1478290725.17134142.1602069275205.JavaMail.zimbra@redhat.com>

Hi Jan,

> ----- Original Message -----
> > This syscall is currently (v5.9) supported on these architectures:
> > arc, csky, mips, m68k, nds32, sh

> > constants are missing for m68k, not sure if the testcase is valid for it.
> > Untested.

> > Test for __LTP__NR_INVALID_SYSCALL saves adding autotools check for
> > <asm/cachectl.h>.

> > Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> > ---
> > Hi,

> > FYI: I was going to ask for removal of this test, but all these archs are
> > still supported. This test compiles on all archs now, but I haven't run
> > it (I don't have access to none of these archs, not sure if LTP is even
> > tested on these archs).

> I haven't tested it too, but rewrite looks good.

> Acked-by: Jan Stancek <jstancek@redhat.com>

Thanks for your review, merged.

Kind regards,
Petr

      reply	other threads:[~2020-10-08 20:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 20:24 [PATCH 1/1] cacheflush01: Rewrite into new API Petr Vorel
2020-10-02 23:38 ` Vineet Gupta
2020-10-07 11:14 ` [LTP] " Jan Stancek
2020-10-08 20:04   ` Petr Vorel [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=20201008200406.GA18136@dell5510 \
    --to=petr.vorel@gmail.com \
    --cc=dalias@libc.org \
    --cc=deanbo422@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=green.hu@gmail.com \
    --cc=guoren@kernel.org \
    --cc=jstancek@redhat.com \
    --cc=linux-csky@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=macro@linux-mips.org \
    --cc=oferle@nvidia.com \
    --cc=vgupta@synopsys.com \
    --cc=ysato@users.sourceforge.jp \
    /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).