From: Jeff Garzik <jeff@garzik.org>
To: Ananda Raju <Ananda.Raju@neterion.com>
Cc: netdev@vger.kernel.org, leonid.grossman@neterion.com,
sivakumar.subramani@neterion.com, alicia.pena@neterion.com,
sreenivasa.honnur@netrion.com, ramkrishna.vepa@neterion.com
Subject: Re: [PATCH 2.6.20 1/5] s2io: updates for s2io driver.
Date: Thu, 18 Jan 2007 12:01:31 -0500 [thread overview]
Message-ID: <45AFA7EB.8060601@garzik.org> (raw)
In-Reply-To: <Pine.GSO.4.10.10701110230560.1618-100000@guinness>
Ananda Raju wrote:
> Hello,
>
> List of changes in this patch:
>
> This patch adds two load parameters napi and ufo. Previously NAPI was
> compilation option with these changes wan enable disable NAPI using load
> parameter. Also we are introducing ufo load parameter to enable/disable
> ufo feature
>
> Signed-off-by: Sivakumar Subramani <sivakumar.subramani@neterion.com>
OK, you're getting closer :)
Problems that need correcting:
1) Your email subject line is a one-line summary of the patch. "s2io:
updates for s2io driver" is useless, because it tells us nothing about
the patch itself. When applied in a series,
git log master..upstream-fixes | git shortlog
will produce
Ananda Raju (5):
s2io: updates for s2io driver
s2io: updates for s2io driver
s2io: updates for s2io driver
s2io: updates for s2io driver
s2io: updates for s2io driver
which clearly makes it impossible to distinguish between changesets.
Please re-read Rule #1 of http://linux.yyz.us/patch-format.html
Also, re-read Rule #2. Everything in your email body before the "---"
terminator is copied DIRECTLY into the kernel changelog. As such,
comments like "Hello," and "List of changes in this patch:" must be
hand-edited out of your email, before applying the patch.
Please fix these problems and resubmit.
Jeff
next prev parent reply other threads:[~2007-01-18 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 7:41 [PATCH 2.6.20 1/5] s2io: updates for s2io driver Ananda Raju
2007-01-18 17:01 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-19 7:55 Sivakumar Subramani
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=45AFA7EB.8060601@garzik.org \
--to=jeff@garzik.org \
--cc=Ananda.Raju@neterion.com \
--cc=alicia.pena@neterion.com \
--cc=leonid.grossman@neterion.com \
--cc=netdev@vger.kernel.org \
--cc=ramkrishna.vepa@neterion.com \
--cc=sivakumar.subramani@neterion.com \
--cc=sreenivasa.honnur@netrion.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).