From: David Brownell <david-b@pacbell.net>
To: David Hollis <dhollis@davehollis.com>
Cc: Michael Helmling <supermihi@web.de>,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] New, yet unsupported USB-Ethernet adaptor
Date: Wed, 3 May 2006 12:23:24 -0700 [thread overview]
Message-ID: <200605031223.25840.david-b@pacbell.net> (raw)
In-Reply-To: <200605031210.35865.david-b@pacbell.net>
On Wednesday 03 May 2006 12:10 pm, David Brownell wrote:
> Well, it's always allowed driver modularization ... the change was only
> to move the hardware-specific parts outside of the driver core.
Bad wording there. Last September I submitted patches to split out
the driver core and the hardware-specific parts into separate source
and object modules ... the core was always separate from the parts
applying to specific hardware. (As you know, since you adopted that
approach for your ASIX code.) What changed was the "one big file"
model, which had stopped making sense.
- Dave
next prev parent reply other threads:[~2006-05-03 19:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 18:02 New, yet unsupported USB-Ethernet adaptor Michael Helmling
2006-05-02 19:13 ` Ioan Ionita
2006-05-02 20:40 ` Ioan Ionita
2006-05-02 21:03 ` Michael Helmling
[not found] ` <d9def9db0605050554m7b1e093di85782c1b09ca2636@mail.gmail.com>
2006-05-06 21:05 ` Michael Helmling
2006-05-02 21:25 ` Oliver Neukum
2006-05-02 22:09 ` [linux-usb-devel] " David Brownell
2006-05-03 5:06 ` Michael Helmling
2006-05-03 5:29 ` David Brownell
2006-05-03 13:28 ` Michael Helmling
2006-05-03 14:44 ` David Hollis
2006-05-03 15:31 ` Andrey Panin
2006-05-03 18:14 ` Michael Helmling
2006-05-03 18:33 ` Pavel Machek
2006-05-03 19:10 ` David Brownell
2006-05-03 19:23 ` David Brownell [this message]
2006-05-03 18:31 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-05-06 23:23 linux
2006-05-08 15:51 ` Markus Rechberger
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=200605031223.25840.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=dhollis@davehollis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=supermihi@web.de \
/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