[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200522172531.va2hi6jqog3a6473@function>
Date: Fri, 22 May 2020 19:25:31 +0200
From: Samuel Thibault <samuel.thibault@...-lyon.org>
To: Joe Perches <joe@...ches.com>
Cc: Dan Carpenter <dan.carpenter@...cle.com>,
MugilRaj <dmugil2000@...il.com>, devel@...verdev.osuosl.org,
Kirk Reiser <kirk@...sers.ca>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
speakup@...ux-speakup.org, linux-kernel@...r.kernel.org,
Chris Brannon <chris@...-brannons.com>
Subject: Re: [PATCH] taging: speakup: remove volatile
Joe Perches, le ven. 22 mai 2020 10:22:03 -0700, a ecrit:
> > Put another way: I don't think putting any hint here would help, on the
> > contrary, somebody has to really look at what protection is needed,
> > without getting influenced by rules-of-thumb.
>
> checkpatch newbies/robots will submit this change again otherwise.
Ah, ok, right.
I don't think removing volatiles is a thing for newbies,
> Comment wording can always be improved.
I'd then suggest
/* TODO: determine what proper synchronization "volatile" should be
* replaced with. */
Samuel
Powered by blists - more mailing lists