From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jody McIntyre <scjody@modernduck.com>
Cc: linux1394-user@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Ben Collins <ben.collins@ubuntu.com>
Subject: ieee1394/oui.db (was Re: [PATCH] ieee1394: allow building with absolute SUBDIRS path)
Date: Tue, 31 Jan 2006 21:19:20 +0100 [thread overview]
Message-ID: <43DFC648.4030404@s5r6.in-berlin.de> (raw)
In-Reply-To: <20060131052101.GC9667@conscoop.ottawa.on.ca>
Jody McIntyre wrote:
> Does anyone else feel like killing oui.c?
I have no strong feelings for or against oui.db. It is nice to have the
vendor names decoded in sysfs, although the footprint is considerable:
$ du oui.o ieee1394.ko
252K oui.o
356K ieee1394.ko
OTOH, nobody is forced to compile it in. And except for the Makefile
patch and .gitignore patch which came in this month, oui.db does not
impose a real maintenance burden. The fact that we are too lazy to
update the db saves us work too. :-)
BTW, oui.db has 7048 entries but IEEE lists 8949 today. Either people
vote oui.db off the island now, or I will submit an update.
--
Stefan Richter
-=====-=-==- ---= =====
http://arcgraph.de/sr/
next prev parent reply other threads:[~2006-01-31 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 0:19 [PATCH] ieee1394: allow building with absolute SUBDIRS path Johannes Berg
2006-01-26 22:28 ` Stefan Richter
2006-01-27 11:31 ` Johannes Berg
2006-01-31 5:21 ` Jody McIntyre
2006-01-31 20:19 ` Stefan Richter [this message]
2006-02-04 4:08 ` ieee1394/oui.db (was Re: [PATCH] ieee1394: allow building with absolute SUBDIRS path) Jody McIntyre
[not found] ` <1138739715.4456.302.camel@grayson>
2006-02-04 8:54 ` Stefan Richter
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=43DFC648.4030404@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=ben.collins@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-user@lists.sourceforge.net \
--cc=scjody@modernduck.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).