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 2/3] serial/ucc_uart: Use .dev.of_node instead of .node in struct of_device
Date: Sun, 2 May 2010 21:00:42 +0400 [thread overview]
Message-ID: <20100502170042.GB14036@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20100502165912.GA11300-wnGakbxT3iijyJ0x5qLZdcN33GVbZNy3@public.gmane.org>
Fixes following build failure:
drivers/serial/ucc_uart.c: In function 'ucc_uart_probe':
drivers/serial/ucc_uart.c:1200: error: 'struct platform_device' has no member named 'node'
Signed-off-by: Anton Vorontsov <avorontsov-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>
---
drivers/serial/ucc_uart.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/serial/ucc_uart.c b/drivers/serial/ucc_uart.c
index fce07be..907b06f 100644
--- a/drivers/serial/ucc_uart.c
+++ b/drivers/serial/ucc_uart.c
@@ -1197,7 +1197,7 @@ static void uart_firmware_cont(const struct firmware *fw, void *context)
static int ucc_uart_probe(struct of_device *ofdev,
const struct of_device_id *match)
{
- struct device_node *np = ofdev->node;
+ struct device_node *np = ofdev->dev.of_node;
const unsigned int *iprop; /* Integer OF properties */
const char *sprop; /* String OF properties */
struct uart_qe_port *qe_port = NULL;
--
1.7.0.5
next prev 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 ` Anton Vorontsov [this message]
2010-05-02 17:00 ` [PATCH 3/3] USB: FHCI: Use .dev.of_node instead of .node in struct of_device Anton Vorontsov
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=20100502170042.GB14036@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