From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
Cc: spi-devel-general@lists.sourceforge.net,
Andrei Konovalov <akonovalov@ru.mvista.com>,
Wolfgang Reissnegger <wre@xilinx.com>,
linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] Simple driver for Xilinx SPI controler.
Date: Wed, 6 Jun 2007 13:55:25 -0600 [thread overview]
Message-ID: <fa686aa40706061255w2e589980tf89f3ba763bb9f54@mail.gmail.com> (raw)
In-Reply-To: <20070606190640.B7028900053@mail104-cpk.bigfish.com>
On 6/6/07, Stephen Neuendorffer <stephen.neuendorffer@xilinx.com> wrote:
> > Why still have XILINX_EDK? I thought you meant replace
> > XILINX_EDK with XILINX_DRIVERS.
>
> Yes, that's what I was suggesting.
> But I think that Andrei still wants to use XILINX_EDK to pull in the
> stuff in drivers/xilinx_common.
>
> # The Xilinx OS common code
> obj-$(CONFIG_XILINX_EDK) += xbasic_types.o xpacket_fifo_l_v2_00_a.o \
> xpacket_fifo_v2_00_a.o xversion.o \
> xdma_channel.o xdma_channel_sg.o
>
> Which you wouldn't want if you were able to build a kernel completely
> from 'non-edk' drivers.
Fair enough, but that's only an issue for vendor trees. None of this
code will be going into mainline. Any of it that does get into good
shape should probably go under drivers/misc, and have the drivers
select only the pieces that are needed (with finer-grain CONFIG_
items). A blanked CONFIG_XILINX_EDK for random stuff is not a good
idea.
Cheers,
g.
>
> Steve
>
>
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-06-06 19:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 14:05 [PATCH] Simple driver for Xilinx SPI controler Andrei Konovalov
2007-06-06 16:03 ` Stephen Neuendorffer
2007-06-06 17:57 ` Andrei Konovalov
2007-06-06 18:06 ` Stephen Neuendorffer
2007-06-06 19:00 ` Grant Likely
2007-06-06 19:06 ` Stephen Neuendorffer
2007-06-06 19:55 ` Grant Likely [this message]
2007-06-07 13:50 ` Andrei Konovalov
2007-06-06 20:49 ` Wolfgang Reissnegger
2007-06-06 20:55 ` Grant Likely
2007-06-07 5:09 ` [spi-devel-general] " David Brownell
2007-06-07 18:39 ` Andrei Konovalov
2007-06-07 19:21 ` David Brownell
2007-06-09 16:58 ` Andrei Konovalov
2007-06-12 16:28 ` David Brownell
2007-06-13 14:55 ` Andrei Konovalov
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=fa686aa40706061255w2e589980tf89f3ba763bb9f54@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=akonovalov@ru.mvista.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=stephen.neuendorffer@xilinx.com \
--cc=wre@xilinx.com \
/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).