[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c23228be48c0416fbec7937c6008a204@intel.com>
Date: Wed, 29 Jun 2022 08:37:13 +0000
From: "Winkler, Tomas" <tomas.winkler@...el.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Usyskin, Alexander" <alexander.usyskin@...el.com>
CC: Jani Nikula <jani.nikula@...ux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@...el.com>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
"Tvrtko Ursulin" <tvrtko.ursulin@...ux.intel.com>,
"Lubart, Vitaly" <vitaly.lubart@...el.com>,
"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v3 13/14] mei: debugfs: add pxp mode to devstate in
debugfs
>
> On Sun, Jun 19, 2022 at 04:37:20PM +0300, Alexander Usyskin wrote:
> > From: Tomas Winkler <tomas.winkler@...el.com>
> >
> > CC: Vitaly Lubart <vitaly.lubart@...el.com>
> > Signed-off-by: Tomas Winkler <tomas.winkler@...el.com>
>
> We can not take patches without any changelog text, you know this :(
Okay, will add some more info.
>
> > ---
> > drivers/misc/mei/debugfs.c | 17 +++++++++++++++++
> > 1 file changed, 17 insertions(+)
> >
> > diff --git a/drivers/misc/mei/debugfs.c b/drivers/misc/mei/debugfs.c
> > index 1ce61e9e24fc..4074fec866a6 100644
> > --- a/drivers/misc/mei/debugfs.c
> > +++ b/drivers/misc/mei/debugfs.c
> > @@ -86,6 +86,20 @@ static int mei_dbgfs_active_show(struct seq_file
> > *m, void *unused) } DEFINE_SHOW_ATTRIBUTE(mei_dbgfs_active);
> >
> > +static const char *mei_dev_pxp_mode_str(enum mei_dev_pxp_mode
> state)
> > +{ #define MEI_PXP_MODE(state) case MEI_DEV_PXP_##state: return
> #state
> > + switch (state) {
> > + MEI_PXP_MODE(DEFAULT);
> > + MEI_PXP_MODE(INIT);
> > + MEI_PXP_MODE(SETUP);
> > + MEI_PXP_MODE(READY);
>
> Just spell out the case and return lines, don't create macros for no good
> reason please.
We use those print macros paradigm consistently int the code, the macro has a very limited scope.
We are aware of wrong sides of macros but this just little of synthetic sugar no some wild usage.
We believe it helps readability, and it keeps the code consistent.
Other usages:
hbm.c:#define MEI_HBM_STATUS(status) case MEI_HBMS_##status: return #status
hbm.c:#define MEI_CL_CS(status) case MEI_CL_CONN_##status: return #status
hbm.c:#define MEI_HBM_STATE(state) case MEI_HBM_##state: return #state
init.c:#define MEI_DEV_STATE(state) case MEI_DEV_##state: return #state
init.c:#define MEI_PG_STATE(state) case MEI_PG_##state: return #state
Thanks
Tomas
Powered by blists - more mailing lists