From: Kumar Gala <galak@kernel.crashing.org>
To: "Rowan, Chad" <Chad.Rowan@thyssenkrupp.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: export-objs in spi Makefile broke in latest linuxppc_2_4_devel [r eposted]?
Date: Wed, 19 Jul 2006 16:16:37 -0500 [thread overview]
Message-ID: <76B8BEDF-4DDE-47BE-AF9D-664544AA1B4A@kernel.crashing.org> (raw)
In-Reply-To: <86EC6E02268B3D4BA41C1B0C61FB14E60B3C8335@mdcexc01.na.ops.local>
On Jul 19, 2006, at 2:13 PM, Rowan, Chad wrote:
> Shouldn't export-objs in drivers/spi be:
>
> export-objs := spi-core.o spi-algo-mpc5xxx.o spi-algo-mpc5xxx-psc.o \
> spi-iti5200.o spi-eval.o
>
> instead of:
>
> export-objs := spi-core.o spi-algo-mpc5xxx.o spi-algo-mpc5200psc.o \
> spi-iti5200.o spi-eval.o
>
> I believe the spi-algo-mpc5200psc.o should be spi-algo-mpc5xxx-psc.o,
> correct?
Are you really serious about linuxppc_2_4_devel? I can't believe
linuxppc_2_4_devel has changed in months (if not over a year).
- k
prev parent reply other threads:[~2006-07-19 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 19:13 export-objs in spi Makefile broke in latest linuxppc_2_4_devel [r eposted]? Rowan, Chad
2006-07-19 21:16 ` Kumar Gala [this message]
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=76B8BEDF-4DDE-47BE-AF9D-664544AA1B4A@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=Chad.Rowan@thyssenkrupp.com \
--cc=linuxppc-embedded@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