linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
To: shuah <shuah@kernel.org>
Cc: bpf@vger.kernel.org, Jiri Benc <jbenc@redhat.com>,
	Jiri Olsa <jolsa@redhat.com>,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 0/3] selftests: lib.mk improvements
Date: Fri, 22 May 2020 18:38:32 +0300	[thread overview]
Message-ID: <CANoWswmZmHo=ha65u=D8XWD7u9decs6FqubPjVu2YOvm6bz-nA@mail.gmail.com> (raw)
In-Reply-To: <4e0d1e4e-9ed2-025c-1164-fd52a88c1ed2@kernel.org>

Hi, Shuah!

On Fri, May 22, 2020 at 6:09 PM shuah <shuah@kernel.org> wrote:
>
> On 5/19/20 8:49 AM, Yauheni Kaliuta wrote:
> > Hi, shuah!
> >
> >>>>>> On Tue, 19 May 2020 07:59:16 -0600, shuah   wrote:
> >
> >   > On 5/15/20 6:00 AM, Yauheni Kaliuta wrote:
> >   >>
> >   >> Yauheni Kaliuta (3):
> >   >> selftests: do not use .ONESHELL
> >   >> selftests: fix condition in run_tests
> >   >> selftests: simplify run_tests
> >   >>
> >   >> tools/testing/selftests/lib.mk | 19 ++++++-------------
> >   >> 1 file changed, 6 insertions(+), 13 deletions(-)
> >   >>
> >
> >   > Quick note that, I will pull these in for 5.8-rc1.
>
> Patches look okay to me, however, just noticed, this series hasn't
> been cc'ed to linux-kselftest. Hence it didn't go through the
> necessary reviews.
>
> Please run get_maintainers and resend the series to everybody the
> script suggests.
>

Sorry for that. Should I resend to the ML?


-- 
WBR, Yauheni


  reply	other threads:[~2020-05-22 15:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200515120026.113278-1-yauheni.kaliuta@redhat.com>
     [not found] ` <689fe06a-c781-e6ed-0544-8023c86fc21a@kernel.org>
     [not found]   ` <xunyblmknfmy.fsf@redhat.com>
2020-05-22 15:09     ` [PATCH v2 0/3] selftests: lib.mk improvements shuah
2020-05-22 15:38       ` Yauheni Kaliuta [this message]
2020-05-26 17:18         ` shuah

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='CANoWswmZmHo=ha65u=D8XWD7u9decs6FqubPjVu2YOvm6bz-nA@mail.gmail.com' \
    --to=yauheni.kaliuta@redhat.com \
    --cc=bpf@vger.kernel.org \
    --cc=jbenc@redhat.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kselftest@vger.kernel.org \
    --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 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).