[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMRc=MesSDBmqLWAWw7gKz_Gaqhwuy7CtFS4gob_8Oy1ztTVHw@mail.gmail.com>
Date: Sun, 10 Dec 2017 19:42:52 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>, Peter Rosin <peda@...ntia.se>,
linux-i2c <linux-i2c@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 1/2] eeprom: at24: fix coding style issues
2017-12-10 13:57 GMT+01:00 Andy Shevchenko <andy.shevchenko@...il.com>:
> On Thu, Dec 7, 2017 at 3:39 PM, Bartosz Golaszewski <brgl@...ev.pl> wrote:
>> Fix issues reported by checkpatch for at24.c.
>
>> +module_param(io_limit, uint, 0000);
>
>> +module_param(write_timeout, uint, 0000);
>
>
> 0 is a pretty much octal number as 0000.
> So, I would prefer not to blindly follow the stupid advise from
> checkpatch, better to teach checkpatch about 0.
>
>
I submitted a patch for that - let's see what checkpatch maintainers say.
Thanks,
Bartosz
Powered by blists - more mailing lists