From: David Woodhouse <dwmw2@infradead.org>
To: miguel@cetuc.puc-rio.br
Cc: mtd@infradead.org
Subject: Re: Integrating 2000 and Millenium drivers
Date: Tue, 15 Aug 2000 08:29:10 +0100 [thread overview]
Message-ID: <2757.966324550@cygnus.co.uk> (raw)
In-Reply-To: <6011381691@mamao.cetuc.puc-rio.br>
miguel@cetuc.puc-rio.br said:
>
> BTW, I've just begin hacking DoC last month, so forgive me if I'm
> missing some good reason why these drivers can't be merged...
There's no particularly good reason to keep them separate if we can merge
them without killing the performance. I split them up so that I could point
people at doc2001.c and say 'There. Make it work if you want to'.
Now that's done, I don't see any particular reason to keep them separate.
Code reuse is wonderful as long as it doesn't mean shitloads of conditional
branches in the inner loop of the access functions. I think we can merge
them without doing that, so why not?
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
prev parent reply other threads:[~2000-08-15 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-14 22:38 Integrating 2000 and Millenium drivers Miguel Freitas
2000-08-15 0:37 ` Brendan J Simon
2000-08-15 7:29 ` David Woodhouse [this message]
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=2757.966324550@cygnus.co.uk \
--to=dwmw2@infradead.org \
--cc=miguel@cetuc.puc-rio.br \
--cc=mtd@infradead.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