From: Greg KH <gregkh@linuxfoundation.org>
To: lkft@linaro.org
Cc: lkft-triage@lists.linaro.org, linux-kselftest@vger.kernel.org,
linux-next@vger.kernel.org, shuah@kernel.org
Subject: Re: [REGRESSION] lkft kselftest for next-20211124
Date: Tue, 18 Jan 2022 17:10:26 +0100 [thread overview]
Message-ID: <YebmcuuckaSr6Tfy@kroah.com> (raw)
In-Reply-To: <0100017e6deccd3f-77964da7-0ebe-4914-b2dd-15e0449aa7fd-000000@email.amazonses.com>
On Tue, Jan 18, 2022 at 04:02:22PM +0000, lkft@linaro.org wrote:
> ## Build
> * kernel: 5.16.0-rc2
Why are you testing an old kernel that is known to have issues?
confused,
greg k-h
prev parent reply other threads:[~2022-01-18 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 16:02 [REGRESSION] lkft kselftest for next-20211124 lkft
2022-01-18 16:10 ` 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=YebmcuuckaSr6Tfy@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=lkft@linaro.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).