From: John Richard Moser <nigelenki@comcast.net>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: binary drivers and development
Date: Thu, 10 Mar 2005 12:19:39 -0500 [thread overview]
Message-ID: <423081AB.5030506@comcast.net> (raw)
In-Reply-To: <20050310164847.GA16430@kroah.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greg KH wrote:
> On Thu, Mar 10, 2005 at 11:28:39AM -0500, John Richard Moser wrote:
>
>>I've been looking at the UDI project[1] and thinking about binary
>>drivers and the like, and wondering what most peoples' take on these are
>>and what impact that UDI support would have on the kernel's development.
>
>
> Please, the UDI stuff has been proven to be broken and wrong. If you
> want to work on it, feel free to do so, just don't expect for anyone to
> accept the UDI layer into the kernel mainline.
>
1. What's broken about it
2. Is it possible to fix it
I require information or else I can't assess things.
> What's that phrase about people forgetting history are doomed...
>
> greg k-h
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
Creative brains are a valuable, limited resource. They shouldn't be
wasted on re-inventing the wheel when there are so many fascinating
new problems waiting out there.
-- Eric Steven Raymond
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCMIGqhDd4aOud5P8RAl+PAJ4ndKTmqyRRc+qaJjPK62HBABb0rgCgjCTR
8kQ9MOOdZiH3FUsNG1Hoe3E=
=NIcs
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-03-10 17:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 16:28 binary drivers and development John Richard Moser
2005-03-10 16:48 ` Greg KH
2005-03-10 17:19 ` John Richard Moser [this message]
2005-03-10 17:24 ` Greg KH
2005-03-10 17:02 ` Ralf Baechle
2005-03-10 17:25 ` John Richard Moser
2005-03-10 17:24 ` John Richard Moser
2005-03-10 20:03 ` Diego Calleja
2005-03-10 20:14 ` John Richard Moser
2005-03-10 21:21 ` Lennart Sorensen
2005-03-10 21:42 ` John Richard Moser
2005-03-10 22:31 ` Lee Revell
2005-03-10 21:59 ` Peter Chubb
2005-03-10 22:32 ` John Richard Moser
2005-03-12 15:53 ` Felipe Alfaro Solana
2005-03-13 5:01 ` John Richard Moser
2005-03-13 7:17 ` Mike Galbraith
2005-03-10 22:45 ` Rik van Riel
2005-03-11 10:39 ` Ben Dooks
2005-03-11 16:39 ` Benedikt Spranger
2005-03-11 16:10 ` Jon Smirl
2005-03-11 9:33 ` [TROLL] " Xavier Bestel
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 4:57 Albert Cahalan
2005-03-19 11:29 ` Eric W. Biederman
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=423081AB.5030506@comcast.net \
--to=nigelenki@comcast.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.