public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Geliang Tang <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: brgerst@gmail.com, hpa@zytor.com, luto@kernel.org,
	tglx@linutronix.de, mingo@kernel.org,
	linux-kernel@vger.kernel.org, geliangtang@163.com
Subject: [tip:x86/apic] x86/irq: Drop unlikely before IS_ERR_OR_NULL
Date: Thu, 1 Oct 2015 02:12:42 -0700	[thread overview]
Message-ID: <tip-a7e705af524d165fe7bc303aee82225c66734885@git.kernel.org> (raw)
In-Reply-To: <03d18502ed7ed417f136c091f417d2d88c147ec6.1443667610.git.geliangtang@163.com>

Commit-ID:  a7e705af524d165fe7bc303aee82225c66734885
Gitweb:     http://git.kernel.org/tip/a7e705af524d165fe7bc303aee82225c66734885
Author:     Geliang Tang <geliangtang@163.com>
AuthorDate: Thu, 1 Oct 2015 10:55:29 +0800
Committer:  Thomas Gleixner <tglx@linutronix.de>
CommitDate: Thu, 1 Oct 2015 11:08:56 +0200

x86/irq: Drop unlikely before IS_ERR_OR_NULL

IS_ERR_OR_NULL already contain an unlikely compiler flag. Drop it.

Signed-off-by: Geliang Tang <geliangtang@163.com>
Cc: Brian Gerst <brgerst@gmail.com>
Cc: Andy Lutomirski <luto@kernel.org>
Link: http://lkml.kernel.org/r/03d18502ed7ed417f136c091f417d2d88c147ec6.1443667610.git.geliangtang@163.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
 arch/x86/kernel/irq_64.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/kernel/irq_64.c b/arch/x86/kernel/irq_64.c
index c767cf2..206d0b9 100644
--- a/arch/x86/kernel/irq_64.c
+++ b/arch/x86/kernel/irq_64.c
@@ -72,7 +72,7 @@ bool handle_irq(struct irq_desc *desc, struct pt_regs *regs)
 {
 	stack_overflow_check(regs);
 
-	if (unlikely(IS_ERR_OR_NULL(desc)))
+	if (IS_ERR_OR_NULL(desc))
 		return false;
 
 	generic_handle_irq_desc(desc);

      parent reply	other threads:[~2015-10-01  9:13 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
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-bot for Geliang Tang [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=tip-a7e705af524d165fe7bc303aee82225c66734885@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=brgerst@gmail.com \
    --cc=geliangtang@163.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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