From: "Ravinandan Arakali" <ravinandan.arakali@s2io.com>
To: "'Jeff Garzik'" <jgarzik@pobox.com>
Cc: "'Francois Romieu'" <romieu@fr.zoreil.com>, <netdev@oss.sgi.com>,
<leonid.grossman@s2io.com>, <raghavendra.koushik@s2io.com>,
<rapuru.sriram@s2io.com>
Subject: RE: [PATCH 2.6.9-rc2 4/8] S2io: hardware fixes
Date: Fri, 8 Oct 2004 17:34:31 -0700 [thread overview]
Message-ID: <004301c4ad97$be6a7010$9810100a@S2IOtech.com> (raw)
In-Reply-To: <41672C96.5050501@pobox.com>
Jeff,
Sorry about that. We'll add the signed-off-by line.
We are sending the patches as and when they are completed.
In the next couple of days, the remaining patches should
be done. Do you want us to send them after all are complete
or is it okay to send each patch as and when completed ?
Thanks,
Ravi
-----Original Message-----
From: Jeff Garzik [mailto:jgarzik@pobox.com]
Sent: Friday, October 08, 2004 5:11 PM
To: ravinandan.arakali@s2io.com
Cc: 'Francois Romieu'; netdev@oss.sgi.com; leonid.grossman@s2io.com;
raghavendra.koushik@s2io.com; rapuru.sriram@s2io.com
Subject: Re: [PATCH 2.6.9-rc2 4/8] S2io: hardware fixes
48 hours passed between patch #3 and patch #4. Is there a problem with
your email system?
Also, your patches do not include the "signed-off-by" line described in
the two documents I referenced. The "signed-off-by" line makes the
lawyers happy.
Since you missed that major legal item, please _read_ the following
documents:
http://linux.yyz.us/patch-format.html (see #5, "Sign your work")
http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
Jeff
next prev parent reply other threads:[~2004-10-09 0:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 23:30 [PATCH 2.6.9-rc2 4/8] S2io: hardware fixes Ravinandan Arakali
2004-10-09 0:11 ` Jeff Garzik
2004-10-09 0:34 ` Ravinandan Arakali [this message]
2004-10-09 0:31 ` Jeff Garzik
2004-10-10 3:24 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2004-10-14 1:14 Ravinandan Arakali
2004-10-14 14:47 ` 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='004301c4ad97$be6a7010$9810100a@S2IOtech.com' \
--to=ravinandan.arakali@s2io.com \
--cc=jgarzik@pobox.com \
--cc=leonid.grossman@s2io.com \
--cc=netdev@oss.sgi.com \
--cc=raghavendra.koushik@s2io.com \
--cc=rapuru.sriram@s2io.com \
--cc=romieu@fr.zoreil.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).