From: "Timur Tabi" <timur@freescale.com>
To: "Scott Wood" <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Pass actual dev ptr to dma_* in ucc and cpm_uart serial
Date: Tue, 9 Sep 2008 13:25:54 -0500 [thread overview]
Message-ID: <ed82fe3e0809091125y77973b83vce52e044f329030e@mail.gmail.com> (raw)
In-Reply-To: <48C58359.5060208@freescale.com>
On Mon, Sep 8, 2008 at 2:56 PM, Scott Wood <scottwood@freescale.com> wrote:
> This patch doesn't change that for cpm2, since port.dev is never
> initialized. :-P
I don't initialize port->dev in the UCC UART driver, but it's still
non-zero, so why isn't it initialized in the CPM UART driver?
(P.S. Becky - please CC: me on any UCC UART or QE LIB patches)
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-09-09 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 19:20 [PATCH] Pass actual dev ptr to dma_* in ucc and cpm_uart serial Becky Bruce
2008-09-08 19:56 ` Scott Wood
2008-09-09 14:22 ` Becky Bruce
2008-09-09 18:25 ` Timur Tabi [this message]
2008-09-09 21:04 ` 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=ed82fe3e0809091125y77973b83vce52e044f329030e@mail.gmail.com \
--to=timur@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).