The 2nd is not the dependency but the commit itself.
Ok, you have more experience which patches should go into 2.6.26 at
that point of time, so it's acceptable for me.
I only brought up that topic again because it's a regression between
2.6.22 and 2.6.23 caused by 5c3391f9f749023a49c64d607da4fb49263690eb.
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
--