All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: "Guilherme G. Piccoli" <gpiccoli@canonical.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: akpm@linux-foundation.org, keescook@chromium.org,
	yzaikin@google.com, mcgrof@kernel.org, kernel@gpiccoli.net
Subject: Re: [PATCH] kernel/watchdog.c: convert {soft/hard}lockup boot parameters to sysctl aliases
Date: Mon, 11 May 2020 12:28:23 +0200	[thread overview]
Message-ID: <03d35861-85c0-4a28-4845-02add0671351@suse.cz> (raw)
In-Reply-To: <20200507214624.21911-1-gpiccoli@canonical.com>

On 5/7/20 11:46 PM, Guilherme G. Piccoli wrote:
> After a recent change introduced by Vlastimil's series [0], kernel is
> able now to handle sysctl parameters on kernel command line; also, the
> series introduced a simple infrastructure to convert legacy boot
> parameters (that duplicate sysctls) into sysctl aliases.
> 
> This patch converts the watchdog parameters softlockup_panic and
> {hard,soft}lockup_all_cpu_backtrace to use the new alias infrastructure.
> It fixes the documentation too, since the alias only accepts values 0
> or 1, not the full range of integers. We also took the opportunity here
> to improve the documentation of the previously converted hung_task_panic
> (see the patch series [0]) and put the alias table in alphabetical order.
> 
> [0] lore.kernel.org/lkml/20200427180433.7029-1-vbabka@suse.cz
> 
> Signed-off-by: Guilherme G. Piccoli <gpiccoli@canonical.com>

Ah, so I did miss some, as the Documentation file doesn't mention there is also
a sysctl for those parameters. Maybe it should?

Anyway, thanks.
Acked-by: Vlastimil Babka <vbabka@suse.cz>

      parent reply	other threads:[~2020-05-11 10:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 21:46 [PATCH] kernel/watchdog.c: convert {soft/hard}lockup boot parameters to sysctl aliases Guilherme G. Piccoli
2020-05-07 23:06 ` Andrew Morton
2020-05-08  2:17   ` Guilherme G. Piccoli
2020-05-11 10:31   ` Vlastimil Babka
2020-05-11 10:28 ` Vlastimil Babka [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=03d35861-85c0-4a28-4845-02add0671351@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=gpiccoli@canonical.com \
    --cc=keescook@chromium.org \
    --cc=kernel@gpiccoli.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=yzaikin@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.