From: Andrew Morton <akpm@osdl.org>
To: Dave Olien <dmo@osdl.org>
Cc: thornber@redhat.com, dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trivial patch to dm-io.c
Date: Wed, 28 Apr 2004 14:57:35 -0700 [thread overview]
Message-ID: <20040428145735.5596a74e.akpm@osdl.org> (raw)
In-Reply-To: <20040427224530.GA16850@osdl.org>
Dave Olien <dmo@osdl.org> wrote:
>
> Here's trivial patches to dm-io.c. Just adds static declarations, and adds
> dm_io_sync_bvec() to the list of EXPORT_SYMBOL functions.
Speaking of trivia...
Could you please avoid using content-free subjects such as "trivial patch
to dm-io.c"? We know that it's a patch, and we can see what files it
touches.
Something like "dm-io.c: add static decls, export dm_io_sync_bvec()" would
be a more useful patch description.
It's better than "Updated CPU hotplug patches for IA64 [Patch 3/7]" though.
Probably a third of the patches I receive have useless summaries and I
have to cook up meaningful ones for them. Which is not a competely bad
thing but it is, on balance, best that the originator prepare the summary.
Make my life a little easier ;) Thanks.
prev parent reply other threads:[~2004-04-28 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 22:45 Dave Olien
2004-04-28 21:57 ` Andrew Morton [this message]
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=20040428145735.5596a74e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dm-devel@redhat.com \
--cc=dmo@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thornber@redhat.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
Powered by JetHome