linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Raghav Dogra <raghav@freescale.com>
To: <linuxppc-dev@lists.ozlabs.org>
Cc: <oss@buserror.net>, <prabhakar.kushwaha@nxp.com>,
	Raghav Dogra <raghav@freescale.com>
Subject: [PATCH 1/3] driver/memory: Removal of deprecated NO_IRQ
Date: Mon, 1 Feb 2016 16:16:36 +0530	[thread overview]
Message-ID: <1454323598-5149-1-git-send-email-raghav@freescale.com> (raw)

Replacing the NO_IRQ macro with 0. If there is no interrupt,
returned value will be 0 regardless of what NO_IRQ is defined.

Signed-off-by: Raghav Dogra <raghav@freescale.com>
---
This patchset is dependent on the IFC deep sleep patch:
https://patchwork.ozlabs.org/patch/564785/

 drivers/memory/fsl_ifc.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/memory/fsl_ifc.c b/drivers/memory/fsl_ifc.c
index f5186fa..054809e 100644
--- a/drivers/memory/fsl_ifc.c
+++ b/drivers/memory/fsl_ifc.c
@@ -262,7 +262,7 @@ static int fsl_ifc_ctrl_probe(struct platform_device *dev)
 
 	/* get the Controller level irq */
 	fsl_ifc_ctrl_dev->irq = irq_of_parse_and_map(dev->dev.of_node, 0);
-	if (fsl_ifc_ctrl_dev->irq == NO_IRQ) {
+	if (fsl_ifc_ctrl_dev->irq == 0) {
 		dev_err(&dev->dev, "failed to get irq resource "
 							"for IFC\n");
 		ret = -ENODEV;
-- 
1.9.1

             reply	other threads:[~2016-02-01 10:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 10:46 Raghav Dogra [this message]
2016-02-01 10:46 ` [PATCH 2/3] driver/memory: Update dependency of IFC for Layerscape Raghav Dogra
2016-05-16  0:21   ` [2/3] " Scott Wood
2016-02-01 10:46 ` [PATCH 3/3] mtd/ifc: Segregate IFC fcm and runtime registers Raghav Dogra
2016-02-01 19:41   ` Li Yang
2016-02-01 20:43     ` Brian Norris
2016-02-01 22:26   ` Scott Wood

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=1454323598-5149-1-git-send-email-raghav@freescale.com \
    --to=raghav@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=oss@buserror.net \
    --cc=prabhakar.kushwaha@nxp.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;
as well as URLs for NNTP newsgroup(s).