From: Sylvain Munaut <tnt@246tNt.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Linux PPC DEV <linuxppc-dev@ozlabs.org>
Subject: [PATCH 0/4] 52xx fixes for 2.6.20
Date: Tue, 2 Jan 2007 23:29:51 +0100 [thread overview]
Message-ID: <1167776995690-git-send-email-tnt@246tNt.com> (raw)
Hello Paul,
This is a set of fixes for the various 52xx platforms I'd like to
see in 2.6.20.
- First patch is just an obvious omission in the serial driver.
Certainly not critical but a simple fix nonetheless.
- The second patch corrects an incorrect usage of device_initcall
Note that it's possible other platforms make the same mistake,
a `grep "device_initcall" arch/powerpc/platforms/* -R` gives several
potential hits. I haven't investigated further though as I don't know
those platforms well enough to know if the use is legit or not.
- The two last patches make the assumption the device tree of the
EFIKA has been fixed properly for linux and allow it to boot using
more common code.
Sylvain
next reply other threads:[~2007-01-02 22:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 22:29 Sylvain Munaut [this message]
2007-01-02 22:29 ` [PATCH 1/4] powerpc/serial: Dispose irq mapping when done in mpc52xx_serial.c Sylvain Munaut
2007-01-02 22:29 ` [PATCH 2/4] powerpc: 52xx, Don't use device_initcall to probe of_platform_bus Sylvain Munaut
2007-01-02 22:29 ` [PATCH 3/4] powerpc: Use common 52xx of_platform probe code for EFIKA Sylvain Munaut
2007-01-02 22:29 ` [PATCH 4/4] powerpc: Restore 'proper' link order in platform Sylvain Munaut
2007-01-02 22:51 ` Grant Likely
2007-01-02 22:53 ` [PATCH 3/4] powerpc: Use common 52xx of_platform probe code for EFIKA Grant Likely
2007-01-09 12:08 ` Paul Mackerras
2007-01-09 22:02 ` Sylvain Munaut
2007-01-11 2:56 ` Benjamin Herrenschmidt
2007-01-02 22:52 ` [PATCH 2/4] powerpc: 52xx, Don't use device_initcall to probe of_platform_bus Grant Likely
2007-01-02 22:51 ` [PATCH 1/4] powerpc/serial: Dispose irq mapping when done in mpc52xx_serial.c Grant Likely
2007-01-09 12:05 ` Paul Mackerras
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=1167776995690-git-send-email-tnt@246tNt.com \
--to=tnt@246tnt.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).