[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c4c6fee41ceb2eb4b583df37ad0d659357cd81d8.camel@perches.com>
Date: Mon, 11 May 2020 10:16:34 -0700
From: Joe Perches <joe@...ches.com>
To: Jakub Kicinski <kuba@...nel.org>, davem@...emloft.net
Cc: netdev@...r.kernel.org, andrew@...n.ch,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v3] checkpatch: warn about uses of ENOTSUPP
On Mon, 2020-05-11 at 10:08 -0700, Jakub Kicinski wrote:
> ENOTSUPP often feels like the right error code to use, but it's
> in fact not a standard Unix error. E.g.:
>
> $ python
> > > > import errno
> > > > errno.errorcode[errno.ENOTSUPP]
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> AttributeError: module 'errno' has no attribute 'ENOTSUPP'
>
> There were numerous commits converting the uses back to EOPNOTSUPP
> but in some cases we are stuck with the high error code for backward
> compatibility reasons.
>
> Let's try prevent more ENOTSUPPs from getting into the kernel.
>
> Recent example:
> https://lore.kernel.org/netdev/20200510182252.GA411829@lunn.ch/
>
> v3 (Joe):
> - fix the "not file" condition.
>
> v2 (Joe):
> - add a link to recent discussion,
> - don't match when scanning files, not patches to avoid sudden
> influx of conversion patches.
> https://lore.kernel.org/netdev/20200511165319.2251678-1-kuba@kernel.org/
>
> v1:
> https://lore.kernel.org/netdev/20200510185148.2230767-1-kuba@kernel.org/
>
> Suggested-by: Andrew Lunn <andrew@...n.ch>
> Signed-off-by: Jakub Kicinski <kuba@...nel.org>
> Acked-by: Joe Perches <joe@...ches.com>
> ---
Thanks.
No worries here and it's not worth a respin, but
typically the patch changelog goes below the --- line.
Powered by blists - more mailing lists