From: Milton Miller <miltonm@bga•com>
To: Paul Mackerras <paulus@samba•org>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: ppcdev <linuxppc-dev@ozlabs•org>
Subject: patches for 2.6.28
Date: Wed, 8 Oct 2008 02:28:13 -0500 [thread overview]
Message-ID: <29d58cf74ce079976ecb583333a442d4@bga.com> (raw)
Ben, Paul
Please merge or comment on the following patches for 2.6.28. They were=20=
originally posted for 2.6.27 as the merge window was opening and got=20
lost in the shuffles. I verified they still applied to Ben's next tree=20=
on 10/5, with minor offsets.
=A0
powerpc: numa.c: always trim to lmb_end_of_DRAM
http://oldpatchwork.ozlabs.org/linuxppc/patch?person=3D79&id=3D19577
powerpc: pseries, cell: use cpu_thread_in_core in smp_init for=20
of_spin_map
http://oldpatchwork.ozlabs.org/linuxppc/patch?person=3D79&id=3D19578
powerpc: find and destroy possible stale kernel added properties
http://oldpatchwork.ozlabs.org/linuxppc/patch?person=3D79&id=3D19579
powerpc: add static and ifdef prom_strtoul and prom_memparse
http://oldpatchwork.ozlabs.org/linuxppc/patch?person=3D79&id=3D19580
thanks,
milton=
reply other threads:[~2008-10-08 7:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=29d58cf74ce079976ecb583333a442d4@bga.com \
--to=miltonm@bga$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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