From: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
To: "Grant Likely" <grant.likely@secretlab.ca>,
"Wolfgang Reissnegger" <wre@xilinx.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: [PATCH 1/3] Add generic configuration option to enable all xilinx drivers.
Date: Wed, 22 Aug 2007 09:35:47 -0700 [thread overview]
Message-ID: <20070822163551.8F0118D0055@mail31-sin.bigfish.com> (raw)
In-Reply-To: <fa686aa40708212028n6dfe02fend98298fc945f063e@mail.gmail.com>
=20
> -----Original Message-----
> From: glikely@secretlab.ca [mailto:glikely@secretlab.ca] On=20
> Behalf Of Grant Likely
> Sent: Tuesday, August 21, 2007 8:28 PM
> To: Wolfgang Reissnegger
> Cc: linuxppc-embedded@ozlabs.org; Stephen Neuendorffer
> Subject: Re: [PATCH 1/3] Add generic configuration option to=20
> enable all xilinx drivers.
>=20
> On 8/21/07, wolfgang.reissnegger@xilinx.com
> <wolfgang.reissnegger@xilinx.com> wrote:
> > From: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
> >
> > In the future, this will be used to provide similar configuration
> > for PowerPC and Microblaze.
>=20
> I'm not convinced that this change is worth it since there is only one
> in-tree driver that uses it. I'd maintain it separately in your tree
> until other drivers or the microblaze stuff is ready for merging.
I have at least one more driver that will use it, for the ICAP, and
joachim's AC97 driver should use it too.
In any event, my intention with all of this is to start small to figure
out how
to do it... Plus I think it will be much easier to manage our tree if
basic
changes like this are merged long before arch/microblaze.
Steve=20
next prev parent reply other threads:[~2007-08-22 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 0:53 [PATCH 1/3] Add generic configuration option to enable all xilinx drivers wolfgang.reissnegger
2007-08-22 3:28 ` Grant Likely
2007-08-22 16:35 ` Stephen Neuendorffer [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-22 0:31 Wolfgang Reissnegger
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=20070822163551.8F0118D0055@mail31-sin.bigfish.com \
--to=stephen.neuendorffer@xilinx.com \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.org \
--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).