From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Vorobiev Dmitri <dmitri.vorobiev@movial.fi>
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: [PATCH] [MIPS] Remove unused header file gio.h
Date: Thu, 27 Nov 2008 11:37:06 +0100 [thread overview]
Message-ID: <20081127103706.GA6929@alpha.franken.de> (raw)
In-Reply-To: <43787.88.114.226.209.1227781466.squirrel@webmail.movial.fi>
On Thu, Nov 27, 2008 at 12:24:26PM +0200, Vorobiev Dmitri wrote:
> > On Wed, Nov 26, 2008 at 03:34:32PM +0200, Dmitri Vorobiev wrote:
> >> Grepping reveals that arch/mips/include/asm/sgi/gio.h is
> >> not used by anyone, so let's delete the orphan header.
> >>
> >> Signed-off-by: Dmitri Vorobiev <dmitri.vorobiev@movial.fi>
> >> ---
> >
> > NAK, I have work in progress, which adds GIO devices and uses this
> > file.
> >
>
> That's interesting news! May I ask you which ones you're working on?
first step is to introduce GIO devices similair to PCI devices. My
current working GIO device is solid impact. I also looked at
supporting Phobos G160 cards, but the current set of 2114x drivers
is not useable for that...
The big missing thing in the GIO framework right now is a bullet proof
detection for non standard GIO cards, like newport and XZ cards. They
don't provide ID information...
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2008-11-27 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 13:34 [PATCH] [MIPS] Remove unused header file gio.h Dmitri Vorobiev
2008-11-27 9:16 ` Thomas Bogendoerfer
2008-11-27 10:24 ` Vorobiev Dmitri
2008-11-27 10:37 ` Thomas Bogendoerfer [this message]
2008-11-27 11:22 ` Ralf Baechle
2008-11-27 11:34 ` Thomas Bogendoerfer
2008-11-27 18:39 ` Kumba
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=20081127103706.GA6929@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=dmitri.vorobiev@movial.fi \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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