From: Vitaly Bordug <vbordug@ru.mvista.com>
To: "Kalle Pokki" <kalle.pokki@iki.fi>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] CPM_UART: Fix non-console initialisation
Date: Thu, 19 Oct 2006 23:51:23 +0400 [thread overview]
Message-ID: <20061019235123.2e542229@localhost.localdomain> (raw)
In-Reply-To: <a425f86c0610191240q3be8bc87q7f20a345e27a5d3d@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Thu, 19 Oct 2006 22:40:27 +0300
Kalle Pokki wrote:
> On 10/19/06, Vitaly Bordug <vbordug@ru.mvista.com> wrote:
> > And we end up with init_portdesc called unconditionally? this would
> > likely break, or at least confuse the code, that uses platform dev
> > to pass resources offsets.
>
> Well now that I look at it again, we should probably do
>
> if (cpm_uart_no == 0)
> cpm_uart_init_portdesc();
>
> to make it at least a little less confusing. Remember that
> init_portdesc() is not called when using platform device, so this
> should not affect those targets using it at all.
>
ok.
> > Personally, I don't care much of compat stuff, unless it is
> > breaking/confusing targets using proper resources...
>
> I'm sure there are still lots of people using the compat mode. As long
> as we have it, it should be kept functional.
I'm not for removing it - just any update to the compat stuff should
not touch platform-managed/ make it more complex/confusing to deal with.
I believe it's cumbersome enough yet :-)
>
>
-Vitaly
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-10-19 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 12:31 [PATCH] CPM_UART: Fix non-console initialisation kalle.pokki
2006-10-19 19:14 ` Vitaly Bordug
2006-10-19 19:40 ` Kalle Pokki
2006-10-19 19:51 ` Vitaly Bordug [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=20061019235123.2e542229@localhost.localdomain \
--to=vbordug@ru.mvista.com \
--cc=kalle.pokki@iki.fi \
--cc=linuxppc-embedded@ozlabs.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