netdev
[Top] [All Lists]

RE: [PATCH 2.6.12.1 1/12] S2io: Code cleanup

To: "'Jeff Garzik'" <jgarzik@xxxxxxxxx>, <raghavendra.koushik@xxxxxxxxxxxx>
Subject: RE: [PATCH 2.6.12.1 1/12] S2io: Code cleanup
From: "Ravinandan Arakali" <ravinandan.arakali@xxxxxxxxxxxx>
Date: Mon, 1 Aug 2005 11:01:50 -0700
Cc: <netdev@xxxxxxxxxxx>, <leonid.grossman@xxxxxxxxxxxx>, <rapuru.sriram@xxxxxxxxxxxx>
Importance: Normal
In-reply-to: <42EC5D96.3050304@pobox.com>
Sender: netdev-bounce@xxxxxxxxxxx
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.

Thanks,
Ravi

-----Original Message-----
From: Jeff Garzik [mailto:jgarzik@xxxxxxxxx]
Sent: Saturday, July 30, 2005 10:12 PM
To: raghavendra.koushik@xxxxxxxxxxxx
Cc: netdev@xxxxxxxxxxx; ravinandan.arakali@xxxxxxxxxxxx;
leonid.grossman@xxxxxxxxxxxx; rapuru.sriram@xxxxxxxxxxxx
Subject: Re: [PATCH 2.6.12.1 1/12] S2io: Code cleanup


patch doesn't seem to apply :(

Can you please resend the entire series, taking into account the
comments WRT patch #5?

Also, I was unable to include your fixes in my 'fixes' branch, whose
speed to upstream kernel is accelerated, because patch #1 was not bug fixes.

If you want your bug fixes to go upstream as rapidly as possible, make
sure they are ordered before the code cleanups and new features.  This
allows me to send the fixes upstream immediately, while allowing further
review and testing of the cleanup/feature patches.

        Jeff





<Prev in Thread] Current Thread [Next in Thread>