linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Misc driver fix for 5.15-rc1
Date: Sun, 12 Sep 2021 12:17:50 -0700	[thread overview]
Message-ID: <202109121213.A47D575@keescook> (raw)
In-Reply-To: <CAHk-=wh7FYyewcJkozsjA95yj0AYvmpMDoZd0RxQ3ZbMMdXUdQ@mail.gmail.com>

On Sun, Sep 12, 2021 at 12:03:35PM -0700, Linus Torvalds wrote:
> Could we please just stop pointlessly printing out kernel version data
> that  is already available other ways? Just do 'dmesg', or 'uname -r'
> or whatever instead of insisting on printing out redundant
> information?

This was done to deal with the various mangling of reports (i.e.
"summaries") I've been getting from CI systems that run LKDTM. It has been
difficult to reliably extract actionable details, so instead I included
it with the test output. And the extra details go the other way too:
frequently folks configuring the CI have no context for why tests fail,
and LKDTM usually has a reasonable amount of information about what
Kconfig settings have gone missing, etc, so those hints are reported as
well.

-- 
Kees Cook

  reply	other threads:[~2021-09-12 19:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-12 14:03 [GIT PULL] Misc driver fix for 5.15-rc1 Greg KH
2021-09-12 19:03 ` Linus Torvalds
2021-09-12 19:17   ` Kees Cook [this message]
2021-09-12 19:22     ` Linus Torvalds
2021-09-12 19:44       ` Kees Cook
2021-09-12 19:55         ` Linus Torvalds
2021-09-12 22:26           ` Kees Cook
2021-09-12 19:16 ` pr-tracker-bot

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=202109121213.A47D575@keescook \
    --to=keescook@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).