From: David Miller <davem@davemloft.net>
To: a@unstable.cc
Cc: kuba@kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vxlan: avoid double unlikely() notation when using IS_ERR()
Date: Thu, 10 Dec 2020 12:45:35 -0800 (PST) [thread overview]
Message-ID: <20201210.124535.572123178373912255.davem@davemloft.net> (raw)
In-Reply-To: <20201210085549.22846-1-a@unstable.cc>
From: Antonio Quartulli <a@unstable.cc>
Date: Thu, 10 Dec 2020 09:55:49 +0100
> The definition of IS_ERR() already applies the unlikely() notation
> when checking the error status of the passed pointer. For this
> reason there is no need to have the same notation outside of
> IS_ERR() itself.
>
> Clean up code by removing redundant notation.
>
> Signed-off-by: Antonio Quartulli <a@unstable.cc>
Applied to net-next, thanks.
prev parent reply other threads:[~2020-12-10 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 8:55 Antonio Quartulli
2020-12-10 20:45 ` David Miller [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=20201210.124535.572123178373912255.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a@unstable.cc \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®