[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21825.12510.810320.403463@quad.stoffel.home>
Date: Wed, 29 Apr 2015 15:28:30 -0400
From: "John Stoffel" <john@...ffel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: John Stoffel <john@...ffel.org>, Harald Hoyer <harald@...hat.com>,
Richard Weinberger <richard.weinberger@...il.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] kdbus for 4.1-rc1
>>>>> "Steven" == Steven Rostedt <rostedt@...dmis.org> writes:
Steven> On Wed, Apr 29, 2015 at 12:26:59PM -0400, John Stoffel wrote:
>>
>> If your customers wnat this feature, you're more than welcome to fork
>> the kernel and support it yourself. Oh wait... Redhat does that
>> already. So what's the problem? Just put it into RHEL (which I use
>> I admit, along with Debian/Mint) and be done with it.
Steven> Red Hat tries very hard to push things upstream. It's policy
Steven> is to not keep things for themselves, but always work with the
Steven> community. That way, everyone benefits. Ideally, we should
Steven> come up with a solution that works for all.
Yeah, I agree they have been good. I'm just reacting to the off the
cuff comment of "my customers need it" which isn't a justification for
this feature, esp when it hasn't been shown to be needed in the
kernel.
We went through alot of this with tux the in-kernel httpd server, and
pushing other stuff out to user-space over the years. Why this needs
to come in isn't clear. Or why not just a small part needing to come
in with the rest in userspace.
John
--
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