Hi all,
Call it a detail, but I see that get_ram_size() calls sometime qualify
their argument as volatile and sometimes not, and this makes checkpatch
complain that volatiles are Bad(tm), which I would like to get fixed.
The prototype for get_ram_size() in is
longget_ram_size
On Thu, Apr 21, 2011 at 3:09 AM, Albert ARIBAUD wrote:
Call it a detail, but I see that get_ram_size() calls sometime qualify
their argument as volatile and sometimes not, and this makes checkpatch
complain that volatiles are Bad(tm), which I would like to get fixed.
The prototype for
Le 21/04/2011 19:02, Mike Frysinger a écrit :
On Thu, Apr 21, 2011 at 3:09 AM, Albert ARIBAUD wrote:
Call it a detail, but I see that get_ram_size() calls sometime qualify
their argument as volatile and sometimes not, and this makes checkpatch
complain that volatiles are Bad(tm), which I would
On Thu, Apr 21, 2011 at 1:50 PM, Albert ARIBAUD wrote:
Le 21/04/2011 19:02, Mike Frysinger a écrit :
On Thu, Apr 21, 2011 at 3:09 AM, Albert ARIBAUD wrote:
Call it a detail, but I see that get_ram_size() calls sometime qualify
their argument as volatile and sometimes not, and this makes
Le 22/04/2011 00:28, Mike Frysinger a écrit :
On Thu, Apr 21, 2011 at 1:50 PM, Albert ARIBAUD wrote:
Le 21/04/2011 19:02, Mike Frysinger a écrit :
On Thu, Apr 21, 2011 at 3:09 AM, Albert ARIBAUD wrote:
Call it a detail, but I see that get_ram_size() calls sometime qualify
their argument as
5 matches
Mail list logo