[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <015e01d6663e$e99e4ec0$bcdaec40$@samsung.com>
Date: Thu, 30 Jul 2020 15:59:04 +0900
From: "Namjae Jeon" <namjae.jeon@...sung.com>
To: "'Tetsuhiro Kohada'" <kohada.t2@...il.com>,
<Kohada.Tetsuhiro@...MitsubishiElectric.co.jp>
Cc: <Mori.Takahiro@...MitsubishiElectric.co.jp>,
<Motai.Hirotaka@...MitsubishiElectric.co.jp>,
"'Sungjong Seo'" <sj1557.seo@...sung.com>,
<linux-fsdevel@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] exfat: retain 'VolumeFlags' properly
> Ping..
Hi Tetsuhiro,
>
> On 2020/07/15 19:06, Tetsuhiro Kohada wrote:
> >> It looks complicated. It would be better to simply set/clear VOLUME DIRTY bit.
> >
> > I think exfat_set_vol_flags() gets a little complicated, because it
> > needs the followings (with bit operation)
> > a) Set/Clear VOLUME_DIRTY.
> > b) Set MEDIA_FAILUR.
>
> How about splitting these into separate functions as below?
>
>
> exfat_set_volume_dirty()
> exfat_set_vol_flags(sb, sbi->vol_flag | VOLUME_DIRTY);
>
> exfat_clear_volume_dirty()
> exfat_set_vol_flags(sb, sbi->vol_flag & ~VOLUME_DIRTY);
Looks good.
>
> exfat_set_media_failure()
> exfat_set_vol_flags(sb, sbi->vol_flag | MEDIA_FAILURE);
Where will this function be called? We don't need to create unused functions in advance...
>
>
> The implementation is essentially the same for exfat_set_vol_flags(), but I think the intention of the
> operation will be easier to understand.
Yes.
Thanks!
>
>
> BR
> ---
> Tetsuhiro Kohada <kohada.t2@...il.com>
Powered by blists - more mailing lists