[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <513FABAD.508@sgi.com>
Date: Tue, 12 Mar 2013 15:26:53 -0700
From: Mike Travis <travis@....com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: "Eric W. Biederman" <ebiederm@...ssion.com>,
Jason Wessel <jason.wessel@...driver.com>,
Dimitri Sivanich <sivanich@....com>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
kgdb-bugreport@...ts.sourceforge.net, x86@...nel.org,
linux-kernel@...r.kernel.org, Tim Bird <tim.bird@...sony.com>,
Anton Vorontsov <anton.vorontsov@...aro.org>,
Sasha Levin <sasha.levin@...cle.com>,
Rusty Russell <rusty@...tcorp.com.au>,
Cong Wang <amwang@...hat.com>,
Stephen Boyd <sboyd@...eaurora.org>,
Al Viro <viro@...iv.linux.org.uk>,
Oleg Nesterov <oleg@...hat.com>,
Serge Hallyn <serge.hallyn@...onical.com>
Subject: Re: [PATCH 05/14] KDB: add more exports for supporting KDB modules
On 3/12/2013 3:13 PM, Greg Kroah-Hartman wrote:
> On Tue, Mar 12, 2013 at 03:03:17PM -0700, Mike Travis wrote:
>> Let me see if I can understand the concept better. By denying
>> an external hardware vendor the use of KDB to support a significant
>> piece of proprietary hardware on Linux, I furthering the interests
>> of Linux and the community how?
>
> Did SGI lawyers really agree to this patch? I consider you running this
> by them if you have any questions as to why we are objecting to this.
> If, after discussing it with them, they still are asking for this
> change, please resend it, with their signed-off-by: on it showing that
> they really want this change.
>
> greg k-h
>
There is nobody else involved believe me. I am just trying to do
the right thing. This is not that big an issue as it has absolutely
no relevance to anything within that patch set. I'm trying to
improve the overall experience of using KDB, which I've found most
helpful in the past to get around some very thorny issues, particularly
in regards to bringing up new hardware. If blocking that usage by
non-GPL modules is what's required, then by all means I'm for it.
But understanding more of why the restriction is in place, would be
very helpful the next time I encounter it.
Thanks,
Mike
--
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