Re: Common [00/16] Sl[auo]b: Common code rework V8

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2 Aug 2012, Glauber Costa wrote:

> That said, unless I am missing something, you seem to have added nothing
> in the middle of the series, all new patches go in the end. Am I right?

Correct.\

> In this case, we could merge patches 1-9 if Pekka is fine with them, and
> then move on.

I'd say take it from the top and merge as much patch as we can get into a
a shapre where we have confidence in the approach being right and the
patches being workable.

The first 2 patches should go directly into the tree since they just
improve debuggability and the second patch actually fixes a memory leak.

The next couple could go into next. Not sure where that would end but we
have a long road to go (and I have lots of patches that have not seen
the daylight yet) and therefore I would suggest to work the next two
weeks on cranking out as much as possible and get what we can into -next.


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]