From: Hendrik 'T4cC0re' Meyer <linux@t4c.dev>
To: ardb@kernel.org
Cc: linux-doc@vger.kernel.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@t4c.dev
Subject: [PATCH] efistub: add efi=quiet parameter to selectively silence efistub alone
Date: Mon, 20 Jan 2025 09:52:43 +0100 [thread overview]
Message-ID: <20250120085243.2990309-1-linux@t4c.dev> (raw)
In-Reply-To: <CAMj1kXEeJattXAkvitfyu3KRRokkSMJZR0xgg_+DG2Mk-tMuoA@mail.gmail.com>
> I'd prefer to just raise the verbosity level of those messages instead.
Agreed. I'll send in a new patch setting the verbosity of those messages one
above the default.
Hendrik
next prev parent reply other threads:[~2025-01-20 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 2:44 [PATCH] efistub: add efi=quiet parameter to selectively silence efistub alone Hendrik 'T4cC0re' Meyer
2025-01-19 17:11 ` Ard Biesheuvel
2025-01-19 17:32 ` Hendrik 'T4cC0re' Meyer
2025-01-20 8:45 ` Ard Biesheuvel
2025-01-20 8:52 ` Hendrik 'T4cC0re' Meyer [this message]
2025-01-20 8:54 ` Ard Biesheuvel
2025-01-20 9:13 ` Hendrik 'T4cC0re' Meyer
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=20250120085243.2990309-1-linux@t4c.dev \
--to=linux@t4c.dev \
--cc=ardb@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).