From: "Ravinandan Arakali" <ravinandan.arakali@neterion.com>
To: "'Jeff Garzik'" <jgarzik@pobox.com>, <raghavendra.koushik@neterion.com>
Cc: <netdev@oss.sgi.com>, <leonid.grossman@neterion.com>,
<rapuru.sriram@neterion.com>
Subject: RE: [PATCH 2.6.12.1 1/12] S2io: Code cleanup
Date: Sun, 7 Aug 2005 13:51:52 -0700 [thread overview]
Message-ID: <000001c59b91$d7f07370$4810100a@pc.s2io.com> (raw)
In-Reply-To: <42EC5D96.3050304@pobox.com>
Jeff,
The entire set of patches have been resent and an additional
patch13 to address earlier comments.
Pls confirm if these patches apply correctly.
Thanks,
Ravi
-----Original Message-----
From: Jeff Garzik [mailto:jgarzik@pobox.com]
Sent: Saturday, July 30, 2005 10:12 PM
To: raghavendra.koushik@neterion.com
Cc: netdev@oss.sgi.com; ravinandan.arakali@neterion.com;
leonid.grossman@neterion.com; rapuru.sriram@neterion.com
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
next prev parent reply other threads:[~2005-08-07 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 22:05 [PATCH 2.6.12.1 1/12] S2io: Code cleanup raghavendra.koushik
2005-07-31 5:11 ` Jeff Garzik
2005-08-01 18:01 ` Ravinandan Arakali
2005-08-07 20:51 ` Ravinandan Arakali [this message]
2005-08-07 21:51 ` Moving... please wait Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000001c59b91$d7f07370$4810100a@pc.s2io.com' \
--to=ravinandan.arakali@neterion.com \
--cc=jgarzik@pobox.com \
--cc=leonid.grossman@neterion.com \
--cc=netdev@oss.sgi.com \
--cc=raghavendra.koushik@neterion.com \
--cc=rapuru.sriram@neterion.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).