[lkml]   [2006]   [Mar]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Slab corruption in 2.6.16-rc5-mm2
    Andrew Morton wrote:
    > Nick Piggin <> wrote:

    >>It isn't Andrew's job to make sure a patch gets to the right place
    >>until it is safely in -mm, and even then he's not always going to
    >>know the severity and importance unless he's told.
    > Is too!

    OK, partially. As this case illustrates, everybody makes mistakes and
    you obviously can't go back and verify you got all the patches because.

    The guy who hits the bug and/or writes the patch can easily see it is
    still not merged and shout.

    >>If it was a patch to "restore" a regression in behaviour, CCs should
    >>at least have gone to the author of the patch that broke it, and the
    >>subsystem maintainers / list / etc as well.
    > I actually merged Lee's patch into -mm, copied James on it and then I
    > dropped it when I saw that it spat rejects against an updated version of
    > James's tree, assuming that it had been merged.
    > Often I'll check that a patch reverts successfully from the upstream tree
    > before dropping it, but for an obvious one like that I guess I didn't
    > bother, and assumed that James had taken it. Only he hadn't - instead he'd
    > gone and merged something else, hence the rejects. Oh well.

    You do a great job, but "push the work out to the end nodes", right?
    That's how we get this network to scale. It is trivial for people to
    verify their important patches have propogated as the release approaches.

    (A little harder for part-timers who aren't in the loop about exactly
    when the release will happen, thanks to our -ridiculous-count release
    system, but still easy compared with your having to double check

    SUSE Labs, Novell Inc.
    Send instant messages to your online friends

    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-03-08 10:06    [W:0.022 / U:7.252 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site