[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87DF341A-1356-4B1B-8D25-14D5B0AAB01D@jic23.retrosnub.co.uk>
Date: Mon, 05 Feb 2018 21:51:44 +0000
From: Jonathan Cameron <jic23@...23.retrosnub.co.uk>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>,
Jonathan Cameron <jic23@...nel.org>, linux-iio@...r.kernel.org,
linux-input@...r.kernel.org
CC: Hartmut Knaack <knaack.h@....de>, Jiri Kosina <jikos@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: hid-sensor-accel-3d: Delete an error message for a failed memory allocation in hid_accel_3d_probe()
On 5 February 2018 18:26:59 GMT, SF Markus Elfring <elfring@...rs.sourceforge.net> wrote:
>> If making changes like this I would suggest only sending one until
>> you have have a response from the relevant maintainer.
>
>The corresponding feedback can become more positive for such
>a transformation pattern after a while, can't it?
Not in that sort of time period.
>
>
>> It would save you time as often these sorts of changes are
>> a matter of personal taste and weighing up of costs vs gains
>> - hence it is not obvious that they will be accepted.
>
>Can the wording “WARNING: Possible unnecessary 'out of memory' message”
>(from the script “checkpatch.pl”) be another incentive?
No. The key word is possible. Check patch is dumb and often gives false positives.
>
>Regards,
>Markus
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Powered by blists - more mailing lists