[lkml]   [2006]   [Dec]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: why are some of my patches being credited to other "authors"?
> but it still leaves an open issue -- once one submits a patch, is there 
> *any* official feedback that one can look for to see if it's been
> accepted/rejected/dropped on the floor/whatever?

You can regularely pull Linus' tree (or the tree of the maintainer you
sent your patch) and see whether your patches still apply cleanly.
Whenever they cause a reject, they need your attention: either they were
applied, or they got out of date because something else changed.
(akpm also sends out automatic notification emails for patches in the -mm
tree based on a similar method.)

> but given that i'm trying to follow the kernel guidelines and keep
> each submission as a logically-related chunk, in many cases, i have to
> wait for one patch to be applied before i can submit the next one.
> and, at the moment, there's no way of knowing what's going on.

Well, you can send out a patch series:
[patch 01/02] Prepare foo for blah
[patch 02/02] Apply blah to foo
Ideally you would finish the patch description for patch 02 with something

This patch depends on [patch 01/02] Prepare foo for blah

But usually people will assume they have to apply the patches in order
even without you explicitly telling them.
Unless you are keen on particular feedback about patch 01 before doing
much work on patch 02, this should work out well.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-12-09 13:43    [W:0.107 / U:0.140 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site