From: Jakub Kicinski <kuba@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: rdunlap@infradead.org, benjamin.poirier@gmail.com,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
leit@meta.com,
netdev@vger.kernel.org (open list:NETWORKING DRIVERS),
linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH net-next v2] netconsole: Enable compile time configuration
Date: Mon, 31 Jul 2023 19:52:58 -0700 [thread overview]
Message-ID: <20230731195258.16b3a53d@kernel.org> (raw)
In-Reply-To: <20230731083542.3665886-1-leitao@debian.org>
On Mon, 31 Jul 2023 01:35:41 -0700 Breno Leitao wrote:
> +config NETCONSOLE_EXTENDED_LOG
> + bool "Set kernel extended message as default"
> + depends on NETCONSOLE
> + default n
> + help
> + Set extended log support for netconsole message. If this option is
> + set, log messages are transmitted with extended metadata header in a
> + format similar to /dev/kmsg. See
> + <file:Documentation/networking/netconsole.rst> for details.
> +
> +config NETCONSOLE_PREPEND_RELEASE
> + bool "Prepend kernel release version in the message"
... by default
> + depends on NETCONSOLE_EXTENDED_LOG
> + default n
> + help
> + Set kernel release to be prepended to each netconsole message by
> + default. If this option is set, the kernel release is prepended into
> + the first field of every netconsole message, so, the netconsole
> + server/peer can easily identify what kernel release is logging each
> + message. See <file:Documentation/networking/netconsole.rst> for
> + details.
I had to look at the code to see what this does, exactly.
I think you either need to make similar changes to
make_netconsole_target() so that instances created via sysfs
have the same default.
Or rewrite the help message to talk about forcing kernel
command line arguments, rather than setting defaults.
--
pw-bot: cr
prev parent reply other threads:[~2023-08-01 2:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 8:35 [PATCH net-next v2] netconsole: Enable compile time configuration Breno Leitao
2023-08-01 2:52 ` Jakub Kicinski [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=20230731195258.16b3a53d@kernel.org \
--to=kuba@kernel.org \
--cc=benjamin.poirier@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=leit@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.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).