[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140506.132501.331724703594119414.davem@davemloft.net>
Date: Tue, 06 May 2014 13:25:01 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: josh@...htriplett.org
Cc: eric.dumazet@...il.com, andi@...stfloor.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
tom.zanussi@...ux.intel.com, ak@...ux.intel.com
Subject: Re: [PATCH 08/24] net, diet: Make TCP metrics optional
From: josh@...htriplett.org
Date: Tue, 6 May 2014 10:21:06 -0700
> On Tue, May 06, 2014 at 01:17:52PM -0400, David Miller wrote:
>> From: josh@...htriplett.org
>> Date: Tue, 6 May 2014 09:45:46 -0700
>>
>> > The kernel can do the same. Consider the idea of analyzing a set of
>> > userspace programs, determining what kernel functionality they do and
>> > don't need, feeding that information into the kernel build process, and
>> > automatically dropping unused bits of the kernel.
>>
>> Please make sure I'm not on the list of people who see reports for
>> bugs reported in that setup.
>>
>> Thanks :-)
>
> Fine by me. Just please allow such a setup to exist. :)
You see, that's the point I'm trying to make, once it's upstream
then it's my problem.
You absolutely must consider the burdon you put upon upstream
maintainers when you ask for things to be included.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists