From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 000/013] sh-sci: platform device, clock and console changes
Date: Fri, 08 May 2009 14:33:12 +0000 [thread overview]
Message-ID: <20090508143312.GB12373@linux-sh.org> (raw)
On Thu, Jan 22, 2009 at 12:13:34AM +0900, Magnus Damm wrote:
> sh-sci: platform device, clock and console changes
>
> [PATCH 001/013] sh-sci: add platform device private data
> [PATCH 002/013] sh-sci: allow single port platform devices
> [PATCH 003/013] sh-sci: remove early_sci_setup()
> [PATCH 004/013] sh-sci: rework serial console support
> [PATCH 005/013] sh-sci: replace sci_init_ports()
> [PATCH 006/013] sh-sci: ioremap() in a single place
> [PATCH 007/013] sh-sci: improve clock framework support
> [PATCH 008/013] sh-sci: use to_sci_port() if possible
> [PATCH 009/013] sh-sci: convert sh2 cpu to single port devices
> [PATCH 010/013] sh-sci: convert sh2a cpus to single port devices
> [PATCH 011/013] sh-sci: convert sh3 cpus to single port devices
> [PATCH 012/013] sh-sci: convert sh4 cpus to single port devices
> [PATCH 013/013] sh-sci: sh4a single port devices and clock support
>
> These patches modify the sh-sci driver / SuperH arch as follows:
> - make one platform device per port
> - rework console code
> - improve clock framework support for SuperH Mobile processors
> - various cleanups
>
> I have a few more patches on top of this that implements early
> printk support using early platform devices.
>
This series took a bit of wiggling to get in to shape, but the bulk of it
is there now, with the exception of all of the single port platform
device patches, as that's not something I have any intention of merging.
next reply other threads:[~2009-05-08 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 14:33 Paul Mundt [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-21 15:13 [PATCH 000/013] sh-sci: platform device, clock and console changes Magnus Damm
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=20090508143312.GB12373@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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