From: Kumar Gala <galak@kernel.crashing.org>
To: Jochen Friedrich <jochen@scram.de>
Cc: Vitaly Bordug <vitb@kernel.crashing.org>,
Scott Wood <scottwood@freescale.com>,
"Kernel, Linux" <linux-kernel@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCHv2 0/8] [POWERPC] 8xx cleanups
Date: Wed, 23 Jan 2008 10:11:01 -0600 [thread overview]
Message-ID: <CA8FFE19-B84A-426B-9B1C-EF0F7C87AE47@kernel.crashing.org> (raw)
In-Reply-To: <4797641F.4000902@scram.de>
On Jan 23, 2008, at 9:58 AM, Jochen Friedrich wrote:
> Hi,
>
> this is a series against paulus for-2.6.25 tree to clean up various
> 8xx related stuff.
> The series can be pulled from git://git.bocc.de/dbox2.git cleanup.
> Patch 6 has been modified to remove the #ifdefs as suggested by
> Arndt Bergmann.
> Patch 8 is a new one.
>
> [POWERPC] Remove unused m8xx_cpm_hostalloc/free/dump()
> [POWERPC] Rename m8xx_pic_init to mpc8xx_pics_init
> [POWERPC] Remove unneeded and misspelled prototype m8xx_calibrate_decr
> [POWERPC] Remove declaration of m8xx_pic_init.
> [POWERPC] Remove sysdev/commproc.h
> [POWERPC] Get rid of conditional includes of board specific setup
> [POWERPC] Rename commproc to cpm1 and cpm2_common.c to cpm2.c
> [POWERPC] Move definition of buffer descriptor to cpm.h
These roughly look good, had a few comments. Don't see any reason why
they can't go in.
What impact do the have on boards in arch/ppc being able to build?
- k
next prev parent reply other threads:[~2008-01-23 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 15:58 Jochen Friedrich
2008-01-23 16:11 ` Kumar Gala [this message]
2008-01-23 17:12 ` Sam Ravnborg
2008-01-23 17:31 ` Jon Loeliger
2008-01-23 18:00 ` Sam Ravnborg
2008-01-23 19:35 ` Josh Boyer
2008-01-23 20:12 ` Sam Ravnborg
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=CA8FFE19-B84A-426B-9B1C-EF0F7C87AE47@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=jochen@scram.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--cc=vitb@kernel.crashing.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
all inboxes | Powered by JetHome®