[lkml]   [2005]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] rmmod notifier chain
"Jan Beulich" <> wrote:
> >> I'd be curious to know how you, considering yourself in my
> position,
> >> would have approached breaking up and submitting that size a
> patch.
> >
> >a) Patches which affect the main kernel but which aren't really
> > debugger-related
> So it was right to start with those...
> >b) Patches which affect the main kernel and which are
> debugger-related
> > (adding hooks, generalising interfaces, refactoring functions,
> etc).
> ... and some of those. But you saying this was more or less the right
> approach puts things in contradiction with the complaints from others
> that consumers of some of the changes weren't immediately visible.
> >c) Finally, one monster patch to add the debugger functionality.
> Maybe
> > split into in vger-sized chunks.

There's confusion here between two separate concepts:

a) How patches should be presented (ie: the splitup)

b) When patches are to be merged into Linus's tree.

I have been discussing a) and you've been discussing b).

Regarding b): general cleanups/fixes/etc can of course go into Linus's tree
in the usual manner.

Preparatory patches for some large feature should be delivered as separate
patches so we can see what they're doing to the kernel but they won't
normally be merged until the same day as the large feature itself.
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: 2005-09-12 09:13    [W:0.029 / U:0.292 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site