[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+CK2bBeBC1T_Bc2gskk90bJogOdg-RK1DHf4odsDj-ck_efyQ@mail.gmail.com>
Date: Mon, 4 May 2020 13:56:04 -0400
From: Pavel Tatashin <pasha.tatashin@...een.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: James Morris <jmorris@...ei.org>, Sasha Levin <sashal@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Kees Cook <keescook@...omium.org>, anton@...msg.org,
ccross@...roid.com, Tony Luck <tony.luck@...el.com>,
robh+dt@...nel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v1 1/3] printk: honor the max_reason field in kmsg_dumper
> Hmm, I didn't realize that enums were allowed to have duplicates. That can
> usually screw up logic. I would recommend making that a define afterward.
>
> #define KMSG_DUMP_MAX KMSG_DUMP_POWEROFF
>
> As is done in other locations of the kernel.
>
Hi Steve,
Sure, I will change it to define.
Thank you,
Pasha
Powered by blists - more mailing lists