From: Finn Thain <fthain@telegraphics.com.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/2] pmac-zilog: add platform driver
Date: Sun, 3 Jan 2010 03:39:25 +1100 (EST) [thread overview]
Message-ID: <alpine.OSX.2.00.1001030255060.414@localhost> (raw)
In-Reply-To: <10f740e81001020443h78c615d2l206b99c386600108@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2338 bytes --]
On Sat, 2 Jan 2010, Geert Uytterhoeven wrote:
> On Tue, Nov 17, 2009 at 10:04, Finn Thain <fthain@telegraphics.com.au>
> wrote:
> > Add platform driver to the pmac-zilog driver for mac 68k, putting the
> > powermac-specific bits inside #ifdef CONFIG_PPC_PMAC.
>
> > --- linux-2.6.31.orig/drivers/serial/pmac_zilog.c 2009-11-17 17:07:28.000000000 +1100
> > +++ linux-2.6.31/drivers/serial/pmac_zilog.c 2009-11-17 17:07:38.000000000 +1100
>
> > @@ -1427,6 +1439,8 @@ static struct uart_ops pmz_pops = {
> > #endif
> > };
> >
> > +#ifdef CONFIG_PPC_PMAC
> > +
> > /*
> > * Setup one port structure after probing, HW is down at this point,
> > * Unlike sunzilog, we don't need to pre-init the spinlock as we don't
> > @@ -1823,6 +1837,88 @@ next:
> > return 0;
> > }
> >
> > +#else
> > +
> > +extern struct platform_device scc_a_pdev, scc_b_pdev;
>
> scripts/checkpatch.pl doesn't like this extern, and it's right.
> Can't this be found using standard platform device/driver matching?
The console initcall and arch initcall order didn't permit me to easily
gather the bootinfo data and populate the platform device resources early
enough. (On powermacs there is the open firmware device tree, but of
course, we don't have one.)
I would like to further adopt the driver model in order to ditch the
macintosh_config global, and I'd also like to have proper nubus device
matching. But I think that the serial console device is a bit exceptional
so I'm not too fussed about these two globals.
Anyway, I don't know of a better way to do the serial console but I'm open
to suggestions.
> BTW, there are a few other minor checkpatch issues with some of the
> other patches in the series, too.
I ran checkpatch on all those patches before I submitted them. I ignored
some of the complaints about whitespace where I felt that checkpatch got
it wrong (space character following tab character, IIRC).
checkpatch found lots of mistakes that I did fix, but it can't determine
the most human readable style in all cases, especially where consistency
with the surrounding code is actually more conducive to readability than
strict but sporadic conformance to simple rules would be.
Finn
>
> Gr{oetje,eeting}s,
>
> Geert
>
next prev parent reply other threads:[~2010-01-02 16:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 9:04 [PATCH 1/2] pmac-zilog: add platform driver Finn Thain
2009-12-23 20:16 ` Geert Uytterhoeven
2010-01-02 12:43 ` Geert Uytterhoeven
2010-01-02 16:39 ` Finn Thain [this message]
2010-01-07 21:05 ` Geert Uytterhoeven
2010-01-08 19:17 ` Geert Uytterhoeven
2010-01-09 3:14 ` fthain
2010-01-07 21:12 ` Geert Uytterhoeven
2010-01-10 12:48 ` [PATCH 1/2] pmac-zilog: add platform driver, version 2 fthain
2010-01-10 16:29 ` [PATCH 1/2] pmac-zilog: add platform driver, version 3 Finn Thain
2010-01-14 13:38 ` Geert Uytterhoeven
2010-01-31 7:25 ` ping, was " fthain
2010-01-31 9:03 ` Geert Uytterhoeven
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=alpine.OSX.2.00.1001030255060.414@localhost \
--to=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linuxppc-dev@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;
as well as URLs for NNTP newsgroup(s).