[MeeGo-dev] Kernel process comment
gregkh at suse.de
Wed Apr 28 13:10:47 CDT 2010
On Wed, Apr 28, 2010 at 09:03:15PM +0300, Ameya Palande wrote:
> On Wed, 2010-04-28 at 19:19 +0200, ext Greg KH wrote:
> > On Wed, Apr 28, 2010 at 07:28:13PM +0300, Ameya Palande wrote:
> > > > As Intel is ultimately responsible for distributing and maintaining this
> > > > kernel tree, having someone within intel to "own" each patch in the same
> > > > manner makes lots of sense as well.
> > >
> > > In Moblin days this was a perfect argument. But things should change
> > > when this kernel became part of MeeGo project which is a joint effort
> > > between Intel and Nokia. Is this insider information which is not made
> > > public that only Intel is ultimately responsible for the kernel?
> > No, not at all. Look at the kernel package, the bugzilla owners of
> > kernel bugs, and who is doing all the work and "ownership" here.
> Again I agree to this when you talk in context of Moblin. Since Moblin
> only had support for Intel hardware you could see all @intel addresses
> everywhere, but now it is not true.
Um, no, actually Moblin was quite different. I maintained the kernel
for Novell's Moblin machines, and only picked a few patches from Intel's
kernel. So this was not in the context of Moblin at all.
> I think Nokia has already started patch submission for N900 support.
Yes, and it looks like it went just fine, right?
> Naturally all the bugs related to this should be assigned to Nokia
> instead of Intel. So I fail to understand your argument about Intel
> doing all the work and all the kernel bugs being assigned to Intel.
I'm saying that Intel is currently the owner of the MeeGo kernel
package, and that if you create a bug in the meego bugzilla against the
kernel package, it gets automatically assigned to an Intel developer.
Hopefully in the future there is a way to handle assigning arm-specific
kernel bugs to a Nokia person, but I don't see that happening at the
moment, do you?
More information about the MeeGo-dev