All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Rui Teng <rui.teng@linux.vnet.ibm.com>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Shuah Khan <shuah@kernel.org>,
	Anton Blanchard <anton@au1.ibm.com>,
	Cyril Bur <cyrilbur@gmail.com>,
	Michael Neuling <mikey@neuling.org>,
	Rui Teng <rui.teng@linux.vnet.ibm.com>
Subject: Re: [PATCH] tools/testing/selftests/powerpc: Add Anton's null_syscall benchmark to the selftests
Date: Tue, 27 Sep 2016 20:18:55 +1000	[thread overview]
Message-ID: <87fuol7ii8.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <1474618460-2656-1-git-send-email-rui.teng@linux.vnet.ibm.com>

Rui Teng <rui.teng@linux.vnet.ibm.com> writes:

> From: Anton Blanchard <anton@au.ibm.com>
>
> Pull in a version of Anton's null_syscall benchmark:
> http://ozlabs.org/~anton/junkcode/null_syscall.c
> Into tools/testing/selftests/powerpc/benchmarks.
>
> Suggested-by: Michael Ellerman <mpe@ellerman.id.au>
> Signed-off-by: Anton Blanchard <anton@au.ibm.com>
> Signed-off-by: Rui Teng <rui.teng@linux.vnet.ibm.com>

Can you please resend this CC'ed to linuxppc-dev, that way patchwork
will see it, which is where I look for patches.

I see that MAINTAINERS doesn't list tools/testing/selftests/powerpc
under the PPC section, which it should, so I'll fix that.

cheers

  reply	other threads:[~2016-09-27 10:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-23  8:14 [PATCH] tools/testing/selftests/powerpc: Add Anton's null_syscall benchmark to the selftests Rui Teng
2016-09-27 10:18 ` Michael Ellerman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-27 14:10 Rui Teng
2019-01-23 14:56 ` christophe.leroy
2019-01-23 14:56   ` Christophe Leroy
2019-01-23 14:56   ` Christophe Leroy
2019-01-23 14:56   ` Christophe Leroy

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=87fuol7ii8.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=anton@au1.ibm.com \
    --cc=cyrilbur@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mikey@neuling.org \
    --cc=rui.teng@linux.vnet.ibm.com \
    --cc=shuah@kernel.org \
    /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.