mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: tao@acc.umu.se, matthias.andree@gmx.de
Cc: alan@lxorguk.ukuu.org.uk, wietse@porcupine.org,
	linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
	netdev@oss.sgi.com
Subject: Re: [PATCH] ioctl SIOCGIFNETMASK: ip alias bug 2.4.9 and 2.2.19
Date: Mon, 10 Sep 2001 23:36:20 +0400 (MSK DST)	[thread overview]
Message-ID: <200109101936.XAA00707@ms2.inr.ac.ru> (raw)
In-Reply-To: <20010910100537.W26627@khan.acc.umu.se> from "David Weinehall" at Sep 10, 1 10:05:37 am

Hello!

> a bad idea after all. Whining about this causing "bloat and maintainance

Listen, let's close this thread. :-)

The patch sent by Matthias is enough small not to speak about some bloat.


And I see no reasons to refuse this: it evidently improves the things
almost without efforts. No matter that this imporvement is not so useful,
as it would happen if I guessed this way from the very beginning.
So that applications will have to worry about compatibility with older
kernels in any case.


(BTW Matthias, while applying it to my tree, I noticed that
it does not check for SIOGGIFNETMASK. It would be better to do this only
when it is meaningful: I see only SIOGGIFNETMASK and SIOGGIFBROADCAST).

Alexey

  parent reply	other threads:[~2001-09-10 19:37 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010906155920.B29583@maggie.dt.e-technik.uni-dortmund.de>
     [not found] ` <200109061554.TAA11031@ms2.inr.ac.ru>
2001-09-06 17:48   ` Matthias Andree
2001-09-06 18:06     ` kuznet
2001-09-06 18:18       ` Wietse Venema
2001-09-06 18:38         ` kuznet
2001-09-06 19:45         ` Alan Cox
2001-09-06 19:59           ` Wietse Venema
2001-09-06 20:20             ` jamal
2001-09-06 20:41               ` Wietse Venema
2001-09-06 20:44                 ` jamal
2001-09-06 21:20                   ` Matthias Andree
2001-09-07  6:11                     ` Patrick Schaaf
2001-09-07  9:24                     ` Henning P. Schmiedehausen
2001-09-07 11:13                       ` Matthias Andree
2001-09-08 13:25                     ` Kai Henningsen
2001-09-06 20:22             ` Alan Cox
2001-09-06 20:38               ` Wietse Venema
2001-09-10 16:11             ` Dennis
2001-09-06 20:13           ` Matthias Andree
2001-09-10  8:05             ` David Weinehall
2001-09-10 12:26               ` Wietse Venema
2001-09-10 12:53                 ` David Weinehall
2001-09-10 13:52                   ` Wietse Venema
2001-09-10 15:18                   ` Matthias Andree
2001-09-10 15:12               ` Matthias Andree
2001-09-10 19:36               ` kuznet [this message]
2001-09-10 20:14                 ` Matthias Andree
2001-09-11 15:22                   ` kuznet
2001-09-11 16:39                     ` Matthias Andree
2001-09-10 20:40                 ` Andi Kleen
2001-09-10 21:19                   ` Matthias Andree
2001-09-11 11:26                   ` Matthias Andree

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=200109101936.XAA00707@ms2.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=matthias.andree@gmx.de \
    --cc=netdev@oss.sgi.com \
    --cc=tao@acc.umu.se \
    --cc=wietse@porcupine.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

all inboxes | Powered by JetHome®