From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2 1/2] [RFC][POWERPC] MPC832x_RDB: update dts to use spi, register mmc_spi stub
Date: Mon, 6 Aug 2007 21:01:51 +0200 [thread overview]
Message-ID: <dc2e2d57444f90b10fdda30fada2ed4f@kernel.crashing.org> (raw)
In-Reply-To: <5C596943-5C01-4097-940C-29FF46E49BA7@kernel.crashing.org>
>> + mmc@0 {
>> + reg = <0>;
>> + pio-handle = <&mmc0pio>;
>> + };
>> };
>
> I'm still against this. Why don't we just do this in
> 83xx/mpc832x_rdb.c
Seconded.
Segher
next prev parent reply other threads:[~2007-08-06 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 17:33 [RFC][PATCH v2 0/2] SPI support for fsl_soc and mpc832x_rdb Anton Vorontsov
2007-08-02 17:35 ` [PATCH v2 1/2] [RFC][POWERPC] MPC832x_RDB: update dts to use spi, register mmc_spi stub Anton Vorontsov
2007-08-02 18:58 ` Kumar Gala
2007-08-06 19:01 ` Segher Boessenkool [this message]
2007-08-02 17:35 ` [PATCH v2 2/2] [RFC][POWERPC] fsl_soc: add support for fsl_spi Anton Vorontsov
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=dc2e2d57444f90b10fdda30fada2ed4f@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--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).