From: "David S. Miller" <davem@davemloft.net>
To: andrew.grover@intel.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
john.ronciak@intel.com, christopher.leech@intel.com
Subject: Re: [RFC] [PATCH 1/3] ioat: DMA subsystem
Date: Wed, 23 Nov 2005 13:51:27 -0800 (PST) [thread overview]
Message-ID: <20051123.135127.127223754.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0511231207410.32487-100000@isotope.jf.intel.com>
Please provide a complete and detailed changelog message for each
patch and an introductory email explaining the top-level purpose of
these changes.
Yes, I personally know what these changes are all about, but not
everyone does.
Sending a bunch of non-descript patches to the list is always a very
bad idea, and will result in little, if any, patch review.
next prev parent reply other threads:[~2005-11-23 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 20:26 [RFC] [PATCH 1/3] ioat: DMA subsystem Andrew Grover
2005-11-23 21:51 ` David S. Miller [this message]
2005-11-23 22:44 ` Jeff Garzik
2005-11-24 15:00 ` Ingo Oeser
2005-11-24 15:04 ` Jeff Garzik
2005-11-28 22:57 ` Andrew Grover
2005-11-24 0:07 ` Greg KH
2005-11-24 11:48 ` Christoph Hellwig
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=20051123.135127.127223754.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew.grover@intel.com \
--cc=christopher.leech@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).