From: Jeff Garzik <garzik@havoc.gtf.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Krzysztof Halasa <khc@pm.waw.pl>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>,
davem@redhat.com
Subject: Re: [PATCH] Generic HDLC patch for 2.5.3
Date: Sat, 2 Feb 2002 20:03:32 -0500 [thread overview]
Message-ID: <20020202200332.A3740@havoc.gtf.org> (raw)
In-Reply-To: <20020202190242.C1740@havoc.gtf.org> <E16XAnc-00010K-00@the-village.bc.nu>
In-Reply-To: <E16XAnc-00010K-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sun, Feb 03, 2002 at 12:46:28AM +0000
On Sun, Feb 03, 2002 at 12:46:28AM +0000, Alan Cox wrote:
> > It adds undiscussed networking changed which I very much doubt DaveM
> > would approve of, and I do not approve of: SIOCDEVICE is far too
> > generic for inclusion, and it adds a structure for passing untyped
> > data which is very definitely non-portable.
>
> You need a very generic structure for WAN interfaces because they have
> ridiculously large numbers of configurable options. These changes were
> discussed over a year ago.
>
> I agree with the comment about untyped data. That does want to be cleaned
> up a chunk more.
Ok... SIOC[GS]WANDEVICE or somesuch?
It could be made more portable and still say generic, IMHO.
Jeff
next prev parent reply other threads:[~2002-02-03 1:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-02 23:33 Krzysztof Halasa
2002-02-03 0:02 ` Jeff Garzik
2002-02-03 0:46 ` Alan Cox
2002-02-03 1:03 ` Jeff Garzik [this message]
2002-02-03 17:13 ` Francois Romieu
2002-02-03 17:46 ` Jeff Garzik
2002-02-03 22:06 ` Francois Romieu
2002-02-04 12:58 ` Krzysztof Halasa
2002-02-04 18:11 ` Francois Romieu
2002-02-05 12:11 ` Krzysztof Halasa
2002-02-04 12:46 ` Krzysztof Halasa
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=20020202200332.A3740@havoc.gtf.org \
--to=garzik@havoc.gtf.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®