Ravinandan Arakali wrote:
Jeff,
We'll re-verify the patches against latest kernel and resend.
Since the remaining 12 patches are layered on top of the first one,
it will be tough to re-order the patches at this stage. Also, we'll
need to rerun the QA cycle to ensure that nothing got broken in
the process of patch reordering.
We will certainly keep this in mind for our next submission.
It's not a problem for me, either way you choose.
I just wanted to make sure you that understood that ordering non-fixes
before fixes could delay the fixes going into the upstream kernel.
Since 2.6.13 is currently in 'release candidate' status, it is only
taking bug fixes right now. If [hypothetically] patches had been
ordered with bug fixes first, I could have sent the fixes into the
2.6.13 release. Without such ordering, we must wait until 2.6.14.
Jeff
|