From: Kumar Gala <galak@kernel.crashing.org>
To: Jon Loeliger <jdl@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 0/5] Remove unnecessary loops_per_jiffy initialization code
Date: Thu, 23 Aug 2007 15:47:14 -0500 [thread overview]
Message-ID: <CF601BCB-6F43-4CE2-A70B-0790DDBB19F7@kernel.crashing.org> (raw)
In-Reply-To: <1187900581.28951.17.camel@ld0161-tx32>
On Aug 23, 2007, at 3:23 PM, Jon Loeliger wrote:
> On Fri, 2007-07-27 at 13:23, Jon Loeliger wrote:
>> This patch series removes lingering jiffies initialization
>> code from several platforms. Note that the first patch in
>> this series for the 86xx has been rebased to current top of
>> Paul's repository and replaces an earlier version.
>>
>>
>> arch/powerpc/platforms/52xx/lite5200.c | 13 ++-----------
>> arch/powerpc/platforms/85xx/mpc85xx_ads.c | 13 -------------
>> arch/powerpc/platforms/85xx/mpc85xx_cds.c | 13 -------------
>> arch/powerpc/platforms/85xx/mpc85xx_mds.c | 11 -----------
>> arch/powerpc/platforms/86xx/mpc86xx_hpcn.c | 14 ++------------
>> arch/powerpc/platforms/8xx/mpc86xads_setup.c | 14 --------------
>> arch/powerpc/platforms/8xx/mpc885ads_setup.c | 14 --------------
>> arch/powerpc/platforms/embedded6xx/holly.c | 12 ------------
>> arch/powerpc/platforms/embedded6xx/prpmc2800.c | 7 -------
>> 9 files changed, 4 insertions(+), 107 deletions(-)
>
> Kumar,
>
> Any reason why patches 1/5 and 2/5, for 86xx and 85xx respectively,
> did not get applied and ushered upstream with the others?
No, I'm glad you said something cause I assumed paul grabbed them all.
I'll grab them in my tree once I beat paul into pulling the include
fixup changes.
- k
next prev parent reply other threads:[~2007-08-23 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 18:23 [PATCH 0/5] Remove unnecessary loops_per_jiffy initialization code Jon Loeliger
2007-08-23 20:23 ` Jon Loeliger
2007-08-23 20:47 ` Kumar Gala [this message]
2007-08-23 21:04 ` Jon Loeliger
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=CF601BCB-6F43-4CE2-A70B-0790DDBB19F7@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=jdl@freescale.com \
--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).