From: Greg KH <greg@kroah.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Veronika Kabatova <vkabatov@redhat.com>,
CKI Project <cki-project@redhat.com>,
Linux Stable maillist <stable@vger.kernel.org>
Subject: Re: ❌ FAIL: Test report for kernel?5.4.0-rc1-643b3a0.cki (stable-next)
Date: Wed, 2 Oct 2019 16:08:24 +0200 [thread overview]
Message-ID: <20191002140824.GA1741376@kroah.com> (raw)
In-Reply-To: <20191002135627.GN17454@sasha-vm>
On Wed, Oct 02, 2019 at 09:56:27AM -0400, Sasha Levin wrote:
> On Wed, Oct 02, 2019 at 07:34:33AM -0400, Veronika Kabatova wrote:
> >
> >
> > ----- Original Message -----
> > > From: "Greg KH" <greg@kroah.com>
> > > To: "CKI Project" <cki-project@redhat.com>
> > > Cc: "Linux Stable maillist" <stable@vger.kernel.org>
> > > Sent: Wednesday, October 2, 2019 7:32:02 AM
> > > Subject: Re: ❌ FAIL: Test report for kernel 5.4.0-rc1-643b3a0.cki (stable-next)
> > >
> > > On Wed, Oct 02, 2019 at 12:27:24AM -0400, CKI Project wrote:
> > > >
> > > > Hello,
> > > >
> > > > We ran automated tests on a recent commit from this kernel tree:
> > > >
> > > > Kernel repo:
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git
> > > > Commit: 643b3a097f86 - selftests: pidfd: Fix undefined
> > > > reference to pthread_create()
> > >
> > > That is 5.4-rc1?
> > >
> > > Why are you sending those results to the stable list?
> > >
> > > confused,
> > >
> >
> > Hi,
> >
> > Sasha has requested to have stable-next tested and results sent to this list:
> >
> > https://gitlab.com/cki-project/pipeline-data/commit/16e0c06addbe62c689782357673f69bb7dff4d9a
>
> Greg, this is the stable-next thing we talked about at LPC; it's just a
> subset of linux-next of stable tagged commits to help us identify issues
> before it actually hits upstream.
>
> I can drop the mails to stable@ if you'd like, but ideally it should
> only be one mail a day.
Ah, ok, I was thinking CKI was testing Linus's tree for some reason and
sending the results only to the stable list, which would be odd. If
this is your stuff, and you get use out of it, that's fine with me, I'll
be quiet :)
thanks,
greg k-h
prev parent reply other threads:[~2019-10-02 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 4:27 ❌ FAIL: Test report for kernel 5.4.0-rc1-643b3a0.cki (stable-next) CKI Project
2019-10-02 5:32 ` Greg KH
2019-10-02 9:55 ` ? " Jakub Racek
2019-10-02 11:34 ` ❌ " Veronika Kabatova
2019-10-02 13:56 ` ❌ FAIL: Test report for kernel?5.4.0-rc1-643b3a0.cki (stable-next) Sasha Levin
2019-10-02 14:08 ` Greg KH [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=20191002140824.GA1741376@kroah.com \
--to=greg@kroah.com \
--cc=cki-project@redhat.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vkabatov@redhat.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;
as well as URLs for NNTP newsgroup(s).