[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <615bb13dc394dac2b56fa60787e1841d2db12462.camel@gmail.com>
Date: Tue, 15 Dec 2020 10:42:36 +0100
From: Bean Huo <huobean@...il.com>
To: Stanley Chu <stanley.chu@...iatek.com>
Cc: alim.akhtar@...sung.com, avri.altman@....com,
asutoshd@...eaurora.org, jejb@...ux.ibm.com,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 3/6] scsi: ufs: Group UFS WB related flags to struct
ufs_dev_info
On Tue, 2020-12-15 at 17:01 +0800, Stanley Chu wrote:
> > + bool wb_buf_flush_enabled;
> > + u8 wb_dedicated_lu;
> > + u8 b_wb_buffer_type;
> > + u32 d_wb_alloc_units;
> > +
> > + bool b_rpm_dev_flush_capable;
> > + u8 b_presrv_uspc_en;
>
> Perhaps we could unify the style of these WB related stuff to wb_* ?
yes, agree. I will change them.
>
> Besides, I am not sure if using tab instead space between the type
> and
> name in this struct is a good idea.
>
using space, in addition single space, type and parameter names are
mixed.
use space:
/* UFS WB related flags */
bool wb_enabled;
bool wb_buf_flush_enabled;
u8
wb_dedicated_lu;
u8 b_wb_buffer_type;
u32 d_wb_alloc_units;
use table:
/* UFS WB related flags */
bool wb_enabled;
bool wb_buf_flush_enabled;
u8 wb_dedicated_lu;
u8 b_wb_buffer_type;
u32 d_wb_alloc_units;
I think, the result is very clear comparing above two examples. yes,
there is no explicit stipulation that we must use space or tab. Both
styles exist in Linux. Maybe this is just matter of personal interest.
Bean
> Thanks,
> Stanley Chu
Powered by blists - more mailing lists