From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linux-embedded@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [RFC] Remove more code when IP_MULTICAST=n
Date: Mon, 25 Aug 2008 08:48:25 +0200 [thread overview]
Message-ID: <20080825084826.19923151@surf> (raw)
In-Reply-To: <Pine.LNX.4.64.0808191618190.25348@vixen.sonytel.be>
Le Tue, 19 Aug 2008 16:18:38 +0200 (CEST),
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com> a écrit :
> On Tue, 19 Aug 2008, Thomas Petazzoni wrote:
> > [RFC] Remove more code when IP_MULTICAST=n
>
> Probably you wanted to cc netdev@vger.kernel.org?
Not necessarly at the beginning: I first wanted to get the feedback of
embedded-concerned developers, who might have a better understanding
than me of the networking stack. Last time I submitted a size-reduction
patch to Dave Miller concerning IGMP, the answer was:
«
I'm not applying this.
This removes core parts of the BSD socket API from applications.
Like TCP and UDP, multicast capabilities are something applications
can always depend upon being available.
If you want a broken networking implementation, you have the source
code, so you can do it in your own tree.
»
So, I'd prefer to send a good patch from the beginning.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2008-08-25 6:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 13:00 [RFC] Remove more code when IP_MULTICAST=n Thomas Petazzoni
2008-08-19 14:18 ` Geert Uytterhoeven
2008-08-25 6:48 ` Thomas Petazzoni [this message]
2008-08-26 3:33 ` Paul Mundt
2008-08-26 16:44 ` Tim Bird
2008-08-28 20:25 ` Alexander Clouter
2008-09-24 15:33 ` Thomas Petazzoni
2008-09-24 17:08 ` Tim Bird
2008-08-25 22:31 ` Mike Frysinger
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=20080825084826.19923151@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=dwmw2@infradead.org \
--cc=linux-embedded@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 NNTP newsgroup(s).