From: David Howells <dhowells@redhat.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: dhowells@redhat.com, akpm@linux-foundation.org,
linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Anna Schumaker <anna.schumaker@netapp.com>,
Boaz Harrosh <ooo@electrozaur.com>,
Christoph Hellwig <hch@lst.de>,
ecryptfs@vger.kernel.org (open list:ECRYPT FILE SYSTEM),
"Eric W. Biederman" <ebiederm@xmission.com>,
Fabian Frederick <fabf@skynet.be>, Joe Perches <joe@perches.com>,
linux-cifs@vger.kernel.org (open list:COMMON INTERNET FILE
SYSTEM (CIFS)),
linux-ext4@vger.kernel.org (open list:EXT4 FILE SYSTEM),
linux-fsdevel@vger.kernel.org (open list:FILESYSTEMS (VFS and
infrastructure)),
linux-nfs@vger.kernel.org (open list:NFS, SUNRPC,
AND LOCKD CLIENTS), Peng Tao <tao.peng@primarydata.com>,
Petr Vandrovec <petr@vandrovec.name>,
samba-technical@lists.samba.org (moderated lis
Subject: Re: [PATCH 12/15] fs: Drop unlikely before IS_ERR(_OR_NULL)
Date: Fri, 31 Jul 2015 10:20:56 +0100 [thread overview]
Message-ID: <396.1438334456@warthog.procyon.org.uk> (raw)
In-Reply-To: <4fd8dd8ed76901a89d6cd17e50ac585ea929f1fb.1438331416.git.viresh.kumar@linaro.org>
Viresh Kumar <viresh.kumar@linaro.org> wrote:
> IS_ERR(_OR_NULL) already contain an 'unlikely' compiler flag and there
> is no need to do that again from its callers. Drop it.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Reviewed-by: David Howells <dhowells@redhat.com>
prev parent reply other threads:[~2015-07-31 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1438331416.git.viresh.kumar@linaro.org>
2015-07-31 8:38 ` [PATCH 12/15] fs: Drop unlikely before IS_ERR(_OR_NULL) Viresh Kumar
2015-07-31 9:20 ` David Howells [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=396.1438334456@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=anna.schumaker@netapp.com \
--cc=ebiederm@xmission.com \
--cc=ecryptfs@vger.kernel.org \
--cc=fabf@skynet.be \
--cc=hch@lst.de \
--cc=joe@perches.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ooo@electrozaur.com \
--cc=petr@vandrovec.name \
--cc=tao.peng@primarydata.com \
--cc=viresh.kumar@linaro.org \
--cc=viro@zeniv.linux.org.uk \
/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).