From: Lennert Buytenhek <buytenh@gnu.org>
To: ultralinux@vger.kernel.org
Subject: Re: [buytenh@gnu.org: [cry for advice] sparc64 bridging troubles]
Date: Wed, 16 Jan 2002 17:57:50 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-101120455203629@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-101068859405697@msgid-missing>
On Wed, Jan 16, 2002 at 09:54:51AM -0800, David S. Miller wrote:
> From: Lennert Buytenhek <buytenh@gnu.org>
> Date: Wed, 16 Jan 2002 12:46:46 -0500
>
> Yup. The attached patch (plus some userspace changes) is what makes
> things tick again, but it's not exactly a marvel of beauty.. :(
>
> I'm not applying this patch ever to my tree. What about other private
> ioctls overloaded to SIOCDEVPRIVATE+3?
I'm not suggesting you should..
> See why none of this SIOCDEVPRIVATE crap can ever work properly?
My point exactly.. glad we understand eachother :-)
cheers,
Lennert
prev parent reply other threads:[~2002-01-16 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 18:49 [buytenh@gnu.org: [cry for advice] sparc64 bridging troubles] Lennert Buytenhek
2002-01-11 8:15 ` David S. Miller
2002-01-16 17:46 ` Lennert Buytenhek
2002-01-16 17:54 ` David S. Miller
2002-01-16 17:57 ` Lennert Buytenhek [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=marc-linux-ultrasparc-101120455203629@msgid-missing \
--to=buytenh@gnu.org \
--cc=ultralinux@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).