From: Jakub Kicinski <kuba@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: davem@davemloft.net, Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH net-next] checkpatch: warn about uses of ENOTSUPP
Date: Mon, 11 May 2020 09:48:19 -0700 [thread overview]
Message-ID: <20200511094819.08f22e84@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <19cc4fe7238358988950970a6f8af68a31b2e4bd.camel@perches.com>
On Sun, 10 May 2020 12:56:53 -0700 Joe Perches wrote:
> On Sun, 2020-05-10 at 11:51 -0700, Jakub Kicinski wrote:
> > Hi Joe, I feel like I already talked to you about this, but I lost
> > my email archive, so appologies if you already said no.
>
> Not so far as I can tell.
>
> This seems OK to me, but using checkpatch -f should probably
> not show this error.
>
> You might include a link to where Andrew Lunn suggested it
> in the commit message. I didn't find it with a trivial search.
Will do.
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> []
> > @@ -4199,6 +4199,14 @@ sub process {
> > "ENOSYS means 'invalid syscall nr' and nothing else\n" . $herecurr);
> > }
> >
> > +# ENOTSUPP is not a standard error code and should be avoided.
> > +# Folks usually mean EOPNOTSUPP (also called ENOTSUP), when they type ENOTSUPP.
> > +# Similarly to ENOSYS warning a small number of false positives is expected.
> > + if ($line =~ /\bENOTSUPP\b/) {
>
> So to avoid having newbies and others trying to convert
> existing uses in files using checkpatch.pl -f, maybe:
Sounds good, thanks!
prev parent reply other threads:[~2020-05-11 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 18:51 [PATCH net-next] checkpatch: warn about uses of ENOTSUPP Jakub Kicinski
2020-05-10 19:04 ` Andrew Lunn
2020-05-10 19:22 ` Jakub Kicinski
2020-05-10 19:56 ` Joe Perches
2020-05-11 16:48 ` Jakub Kicinski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200511094819.08f22e84@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).