From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] 303cc571d1: ltp.setns01.fail
Date: Tue, 16 Jun 2020 04:08:52 -0400 (EDT) [thread overview]
Message-ID: <348139455.16141709.1592294932212.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200615213843.2ojgm3ob7kp3qq6a@wittgenstein>
----- Original Message -----
> I'll send a pr for this to Linus this week (or next since I'm on
> vacation this week) and get this fixed. Thanks for spotting this. What's
> the Reported-by: line format that LTP uses?
I'm not sure we ever used one, it's usually various CI systems that
reference LTP. This thread has been started by kernel test robot:
Reported-by: kernel test robot <rong.a.chen@intel.com>
WARNING: multiple messages have this Message-ID (diff)
From: Jan Stancek <jstancek@redhat.com>
To: lkp@lists.01.org
Subject: Re: [LTP] 303cc571d1: ltp.setns01.fail
Date: Tue, 16 Jun 2020 04:08:52 -0400 [thread overview]
Message-ID: <348139455.16141709.1592294932212.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200615213843.2ojgm3ob7kp3qq6a@wittgenstein>
[-- Attachment #1: Type: text/plain, Size: 421 bytes --]
----- Original Message -----
> I'll send a pr for this to Linus this week (or next since I'm on
> vacation this week) and get this fixed. Thanks for spotting this. What's
> the Reported-by: line format that LTP uses?
I'm not sure we ever used one, it's usually various CI systems that
reference LTP. This thread has been started by kernel test robot:
Reported-by: kernel test robot <rong.a.chen@intel.com>
WARNING: multiple messages have this Message-ID (diff)
From: Jan Stancek <jstancek@redhat.com>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: Cyril Hrubis <chrubis@suse.cz>,
kernel test robot <rong.a.chen@intel.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Jann Horn <jannh@google.com>, LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, Aleksa Sarai <cyphar@cyphar.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
ltp@lists.linux.it, Serge Hallyn <serge@hallyn.com>
Subject: Re: [LTP] 303cc571d1: ltp.setns01.fail
Date: Tue, 16 Jun 2020 04:08:52 -0400 (EDT) [thread overview]
Message-ID: <348139455.16141709.1592294932212.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200615213843.2ojgm3ob7kp3qq6a@wittgenstein>
----- Original Message -----
> I'll send a pr for this to Linus this week (or next since I'm on
> vacation this week) and get this fixed. Thanks for spotting this. What's
> the Reported-by: line format that LTP uses?
I'm not sure we ever used one, it's usually various CI systems that
reference LTP. This thread has been started by kernel test robot:
Reported-by: kernel test robot <rong.a.chen@intel.com>
next prev parent reply other threads:[~2020-06-16 8:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 8:58 [LTP] 303cc571d1: ltp.setns01.fail kernel test robot
2020-06-15 8:58 ` kernel test robot
2020-06-15 8:58 ` kernel test robot
2020-06-15 9:18 ` [LTP] " Cyril Hrubis
2020-06-15 9:18 ` Cyril Hrubis
2020-06-15 9:18 ` Cyril Hrubis
2020-06-15 14:03 ` Jan Stancek
2020-06-15 14:03 ` Jan Stancek
2020-06-15 14:03 ` Jan Stancek
2020-06-15 21:38 ` Christian Brauner
2020-06-15 21:38 ` Christian Brauner
2020-06-16 8:08 ` Jan Stancek [this message]
2020-06-16 8:08 ` Jan Stancek
2020-06-16 8:08 ` Jan Stancek
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=348139455.16141709.1592294932212.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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.