From: Manoj Kumar <manoj@linux.vnet.ibm.com>
To: Geliang Tang <geliangtang@163.com>,
"James E.J. Bottomley" <JBottomley@odin.com>,
Michael Neuling <mikey@neuling.org>,
Wen Xiong <wenxiong@linux.vnet.ibm.com>,
"Matthew R. Ochs" <mrochs@linux.vnet.ibm.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] cxlflash: drop unlikely before IS_ERR_OR_NULL
Date: Thu, 1 Oct 2015 08:00:18 -0500 [thread overview]
Message-ID: <560D2E62.7040600@linux.vnet.ibm.com> (raw)
In-Reply-To: <7685ffa3f47126617d740292cf35bf92cda193c3.1443667610.git.geliangtang@163.com>
Geliang:
Thanks for catching this.
- Manoj
Acked-by: Manoj Kumar <manoj@linux.vnet.ibm.com>
On 9/30/2015 9:55 PM, Geliang Tang wrote:
> IS_ERR_OR_NULL already contain an unlikely compiler flag. Drop it.
>
> Signed-off-by: Geliang Tang <geliangtang@163.com>
> ---
> drivers/scsi/cxlflash/superpipe.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/scsi/cxlflash/superpipe.c b/drivers/scsi/cxlflash/superpipe.c
> index f1b62ce..eb1b01e 100644
> --- a/drivers/scsi/cxlflash/superpipe.c
> +++ b/drivers/scsi/cxlflash/superpipe.c
> @@ -1307,7 +1307,7 @@ static int cxlflash_disk_attach(struct scsi_device *sdev,
> }
>
> ctx = cxl_dev_context_init(cfg->dev);
> - if (unlikely(IS_ERR_OR_NULL(ctx))) {
> + if (IS_ERR_OR_NULL(ctx)) {
> dev_err(dev, "%s: Could not initialize context %p\n",
> __func__, ctx);
> rc = -ENODEV;
> @@ -1432,7 +1432,7 @@ static int recover_context(struct cxlflash_cfg *cfg, struct ctx_info *ctxi)
> struct afu *afu = cfg->afu;
>
> ctx = cxl_dev_context_init(cfg->dev);
> - if (unlikely(IS_ERR_OR_NULL(ctx))) {
> + if (IS_ERR_OR_NULL(ctx)) {
> dev_err(dev, "%s: Could not initialize context %p\n",
> __func__, ctx);
> rc = -ENODEV;
>
next prev parent reply other threads:[~2015-10-01 13:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 2:55 [PATCH 1/3] x86/irq: drop unlikely before IS_ERR_OR_NULL Geliang Tang
2015-10-01 2:55 ` [PATCH 2/3] Input: alps: " Geliang Tang
2015-10-01 2:55 ` [PATCH 3/3] cxlflash: " Geliang Tang
2015-10-01 13:00 ` Manoj Kumar [this message]
2015-10-01 14:49 ` Matthew R. Ochs
2015-10-01 7:30 ` [PATCH 2/3] Input: alps: " Pali Rohár
2015-10-02 18:29 ` Dmitry Torokhov
2015-10-01 9:12 ` [tip:x86/apic] x86/irq: Drop " tip-bot for Geliang Tang
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=560D2E62.7040600@linux.vnet.ibm.com \
--to=manoj@linux.vnet.ibm.com \
--cc=JBottomley@odin.com \
--cc=geliangtang@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mikey@neuling.org \
--cc=mrochs@linux.vnet.ibm.com \
--cc=wenxiong@linux.vnet.ibm.com \
/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