[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vfe3xBuG91=XdZ4zXhfhz4KDwCL9xonSyoH8PuqUgO-+Q@mail.gmail.com>
Date: Thu, 14 Sep 2023 11:44:20 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Hans de Goede <hdegoede@...hat.com>
Cc: Steve Wahl <steve.wahl@....com>,
Justin Ernst <justin.ernst@....com>,
Kyle Meyer <kyle.meyer@....com>,
Dimitri Sivanich <dimitri.sivanich@....com>,
Russ Anderson <russ.anderson@....com>,
Darren Hart <dvhart@...radead.org>,
Andy Shevchenko <andy@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H . Peter Anvin" <hpa@...or.com>, x86@...nel.org,
linux-kernel@...r.kernel.org, Justin Stitt <justinstitt@...gle.com>
Subject: Re: [PATCH v2] x86/platform/uv: Rework NMI "action" modparam handling
On Thu, Sep 14, 2023 at 11:42 AM Andy Shevchenko
<andy.shevchenko@...il.com> wrote:
> On Wed, Sep 13, 2023 at 9:01 PM Hans de Goede <hdegoede@...hat.com> wrote:
...
> > - pr_err("UV: Invalid NMI action:%s, valid actions are:\n", arg);
> > + pr_err("UV: Invalid NMI action:%s, valid actions are:\n", val);
>
> As mentioned previously the val may or may not have a new line in it.
> I dunno about comma removal, but a new line presence can be easily checked.
>
> Either way it's not so critical, hence removing comma. or replacing it
> by '-' (dash) may be enough.
Or even
pr_err("UV: Invalid NMI action:%s --> valid actions are:\n", val);
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists