From: "Shreeya Patel" <shreeya.patel@collabora.com>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
kernelci@lists.linux.dev,
"Gustavo Padovan" <gustavo.padovan@collabora.com>,
"Ricardo Cañuelo Navarro" <ricardo.canuelo@collabora.com>
Subject: Re: KernelCI stable-rc/linux-6.1.y report (19/12/2023)
Date: Wed, 20 Dec 2023 09:38:57 +0000 [thread overview]
Message-ID: <7aff-6582b600-1-597f2100@46892259> (raw)
In-Reply-To: <2023121951-clatter-flatfoot-35e9@gregkh>
On Wednesday, December 20, 2023 00:42 IST, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Tue, Dec 19, 2023 at 12:44:59PM +0000, Shreeya Patel wrote:
> > Hi Everyone,
> >
> > Please find the KernelCI report for stable-rc/linux-6.1.y for this week.
> >
> > ## stable-rc HEAD for linux-6.1.y:
> >
> > Date: 2023-12-18
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/?h=d4e0eced630816f1c7a6d389a4cb6233a606eeea
> >
> > ## Build failures:
> >
> > No build failures seen for the stable-rc/linux-6.1.y commit head \o/
> >
> > ## Boot failures:
> >
> > No **new** boot failures seen for the stable-rc/linux-6.1.y commit head \o/
> >
> > Tested-by: kernelci.org bot <bot@kernelci.org>
>
> These are great, thank you for doing this!
>
> But, any chance you can provide these as a response to the -rc email
> announcement so my tools can pick them up for the commit message? I can
> mush them in here by hand this time, but doing it twice a week for the
> next 10+ years is going to be a pain for me :)
>
Sure, I'll send reports as a response to each of your -rc email announcements
from next time.
Thanks,
Shreeya Patel
> thanks,
>
> greg k-h
prev parent reply other threads:[~2023-12-20 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 12:44 KernelCI stable-rc/linux-6.1.y report (19/12/2023) Shreeya Patel
2023-12-19 19:12 ` Greg KH
2023-12-20 9:38 ` Shreeya Patel [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=7aff-6582b600-1-597f2100@46892259 \
--to=shreeya.patel@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo.padovan@collabora.com \
--cc=kernelci@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=ricardo.canuelo@collabora.com \
--cc=stable@vger.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