[Meego-kernel] Question about upstream patches

[Greg KH]

On Tue, Oct 12, 2010 at 09:10:26AM +0100, Caillaud, Christian wrote:
> Greg,
> 
> I would like to ask some stupid questions and i hope you'll answer.

Why me, I'm not the meego kernel maintainer :)

> If I need to submit a patch which has been already "upstreamed" in
> linux-next for example, do you want me to resend the complete patch
> (with all necessary information which is compliant to kernel patch
> submission standards) and the git commit id, or the commit id with the
> patch description is sufficient itself ?
> Does it apply to patches submitted to linux patchwork sub projects as
> well (e.g. linux-wireless) ?
> If so, does it mean that you'll rebase the patch (or at least the git
> commit id) which I'll submit to this mailing list ?
> Otherwise do I need to backport my "upstream" patch with the meego
> latest kernel version before sumitting it to this mailing list ?

I have no idea, as there seems to be no documented "procedure" for the
MeeGo kernel at all.

These are all great questions, perhaps the proper people will answer
them...

thans,

greg k-h