| To: | Ralf Baechle <ralf@linux-mips.org> |
|---|---|
| Subject: | Re: [PATCH] GIO bus support for SGI IP22/28 |
| From: | Thomas Bogendoerfer <tsbogend@alpha.franken.de> |
| Date: | Thu, 20 Oct 2011 21:07:02 +0200 |
| Cc: | Geert Uytterhoeven <geert@linux-m68k.org>, linux-mips@linux-mips.org |
| In-reply-to: | <20111020174922.GC885@linux-mips.org> |
| References: | <20111020150859.6072A1DA26@solo.franken.de> <20111020161908.GA13220@linux-mips.org> <CAMuHMdXuOAgwPKTUjBCp3t1_kWoJsiwGf=uQfmYP_o+t7JYxUA@mail.gmail.com> <20111020174922.GC885@linux-mips.org> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.20 (2009-06-14) |
On Thu, Oct 20, 2011 at 06:49:22PM +0100, Ralf Baechle wrote: > There may have been obscure prototypes at SGI but I doubt any non-MIPS > GIO systems ever reached production status. wikipedia only mentions MIPS based stuff from SGI with GIO. > > If yes, you want to move it to drivers/gio/. > > Good point - it probably should go there anyway. does a single file really need it's own directoy ? GIO is pretty simple and most of the magic lies inside the board specific parts. My idea is to factor out the common code as soon as IP12/IP20 support comes up (which is probably never). Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ] |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] GIO bus support for SGI IP22/28, Ralf Baechle |
|---|---|
| Next by Date: | [PATCH v2] GIO bus support for SGI IP22/28, Thomas Bogendoerfer |
| Previous by Thread: | Re: [PATCH] GIO bus support for SGI IP22/28, Ralf Baechle |
| Next by Thread: | [PATCH v2] GIO bus support for SGI IP22/28, Thomas Bogendoerfer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |