Devicetree
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: [PATCH 3/3] USB: FHCI: Use .dev.of_node instead of .node in struct of_device
Date: Sun, 2 May 2010 21:00:44 +0400	[thread overview]
Message-ID: <20100502170044.GC14036@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20100502165912.GA11300-wnGakbxT3iijyJ0x5qLZdcN33GVbZNy3@public.gmane.org>

Fixes following build failure:

drivers/usb/host/fhci-hcd.c: In function 'of_fhci_probe':
drivers/usb/host/fhci-hcd.c:568: error: 'struct platform_device' has no member named 'node'
drivers/usb/host/fhci-hcd.c:673: error: 'struct platform_device' has no member named 'node'

Signed-off-by: Anton Vorontsov <avorontsov-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>
---
 drivers/usb/host/fhci-hcd.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/usb/host/fhci-hcd.c b/drivers/usb/host/fhci-hcd.c
index 84adca4..7b5c626 100644
--- a/drivers/usb/host/fhci-hcd.c
+++ b/drivers/usb/host/fhci-hcd.c
@@ -565,7 +565,7 @@ static int __devinit of_fhci_probe(struct of_device *ofdev,
 				   const struct of_device_id *ofid)
 {
 	struct device *dev = &ofdev->dev;
-	struct device_node *node = ofdev->node;
+	struct device_node *node = dev->of_node;
 	struct usb_hcd *hcd;
 	struct fhci_hcd *fhci;
 	struct resource usb_regs;
@@ -670,7 +670,7 @@ static int __devinit of_fhci_probe(struct of_device *ofdev,
 	}
 
 	for (j = 0; j < NUM_PINS; j++) {
-		fhci->pins[j] = qe_pin_request(ofdev->node, j);
+		fhci->pins[j] = qe_pin_request(node, j);
 		if (IS_ERR(fhci->pins[j])) {
 			ret = PTR_ERR(fhci->pins[j]);
 			dev_err(dev, "can't get pin %d: %d\n", j, ret);
-- 
1.7.0.5

  parent reply	other threads:[~2010-05-02 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201004272111.o3RLBw1f020037@imap1.linux-foundation.org>
     [not found] ` <1272428830.24542.72.camel@pasglop>
     [not found]   ` <20100430174240.GA29769@oksana.dev.rtsoft.ru>
     [not found]     ` <s2ifa686aa41004301043uca9bfbafz6db2402bfa233de4@mail.gmail.com>
     [not found]       ` <20100430174609.GA31455@oksana.dev.rtsoft.ru>
     [not found]         ` <n2yfa686aa41004302350i32d385e7gc00b49f39de417cb@mail.gmail.com>
     [not found]           ` <n2yfa686aa41004302350i32d385e7gc00b49f39de417cb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-02 16:59             ` [patch 1/6] gpiolib: introduce chip addition/removal notifier Anton Vorontsov
     [not found]               ` <20100502165912.GA11300-wnGakbxT3iijyJ0x5qLZdcN33GVbZNy3@public.gmane.org>
2010-05-02 17:00                 ` [PATCH 1/3] powerpc/83xx/mcu: Add OF match table Anton Vorontsov
2010-05-02 17:00                 ` [PATCH 2/3] serial/ucc_uart: Use .dev.of_node instead of .node in struct of_device Anton Vorontsov
2010-05-02 17:00                 ` Anton Vorontsov [this message]
2010-05-02 19:34                 ` [patch 1/6] gpiolib: introduce chip addition/removal notifier Grant Likely

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=20100502170044.GC14036@oksana.dev.rtsoft.ru \
    --to=avorontsov-igf4poytycdqt0dzr+alfa@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.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