[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240117185909.78bb633ea090f74de9f4f3b7@hugovil.com>
Date: Wed, 17 Jan 2024 18:59:09 -0500
From: Hugo Villeneuve <hugo@...ovil.com>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: gregkh@...uxfoundation.org, jirislaby@...nel.org,
cosmin.tanislav@...log.com, shc_work@...l.ru, linux-kernel@...r.kernel.org,
linux-serial@...r.kernel.org, Hugo Villeneuve <hvilleneuve@...onoff.com>
Subject: Re: [PATCH 15/18] serial: max310x: replace ENOTSUPP with preferred
EOPNOTSUPP (checkpatch)
On Thu, 18 Jan 2024 01:24:11 +0200
Andy Shevchenko <andy.shevchenko@...il.com> wrote:
> On Thu, Jan 18, 2024 at 12:39 AM Hugo Villeneuve <hugo@...ovil.com> wrote:
> >
> > From: Hugo Villeneuve <hvilleneuve@...onoff.com>
> >
> > Fixes the following checkpatch warning:
> >
> > WARNING: ENOTSUPP is not a SUSV4 error code, prefer EOPNOTSUPP
>
> NAK.
> It's a false positive.
>
> > According to include/linux/errno.h, ENOTSUPP is
> > "Defined for the NFSv3 protocol", so replace it with preferred EOPNOTSUPP.
>
> The GPIO subsystem uses this internal error code internally. User
> space won't get it, so users may not see this one.
Hi Andy,
I will drop the patch then.
What about adding a comment to prevent future fixes?
- return -ENOTSUPP;
+ return -ENOTSUPP; /*
+ * ENOTSUPP is used for backward compatibility
+ * with GPIO subsystem.
+ */
Hugo Villeneuve
Powered by blists - more mailing lists