All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Taht <dave@taht.net>
To: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Cc: dave.taht@gmail.com
Subject: Re: [PATCH] Allow class-e address assignment via ifconfig ioctl
Date: Sat, 15 Dec 2018 17:22:52 -0800	[thread overview]
Message-ID: <87sgyye043.fsf@taht.net> (raw)
In-Reply-To: <20181214.153941.143117737784048381.davem@davemloft.net> (David Miller's message of "Fri, 14 Dec 2018 15:39:41 -0800 (PST)")

David Miller <davem@davemloft.net> writes:

> From: Dave Taht <dave.taht@gmail.com>
> Date: Tue, 11 Dec 2018 15:30:34 -0800
>
>> While most distributions long ago switched to the iproute2 suite
>> of utilities, which allow class-e (240.0.0.0/4) address assignment,
>> distributions relying on busybox, toybox and other forms of
>> ifconfig cannot assign class-e addresses without this kernel patch.
>> 
>> While CIDR has been obsolete for 2 decades, and a survey of all the
>> open source code in the world shows the IN_whatever macros are also
>> obsolete... rather than obsolete CIDR from this ioctl entirely, this
>> patch merely enables class-e assignment, sanely.
>> 
>> Signed-off-by: Dave Taht <dave.taht@gmail.com>
>
> Applied, thanks Dave.

Thanks, but...

Into what tree did you pull it? it's not in net-next as I speak.

I reworked it a bit, giving a hat tip to Vince Fuller and his original
    patch here: https://lkml.org/lkml/2008/1/7/370

http://www.taht.net/classe/0001-linux-kernel-Allow-class-e-address-assignment-via-ifconfig-ioctl.patch

and was minutes away from submitting that version when you took this.

  reply	other threads:[~2018-12-16  1:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 23:30 [PATCH] Allow class-e address assignment via ifconfig ioctl Dave Taht
2018-12-14 23:39 ` David Miller
2018-12-16  1:22   ` Dave Taht [this message]
2018-12-16  2:25     ` David Miller

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=87sgyye043.fsf@taht.net \
    --to=dave@taht.net \
    --cc=dave.taht@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@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.