netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [PATCH] sfc fix for 2.6.27
Date: Tue, 10 Jun 2008 18:12:57 -0400	[thread overview]
Message-ID: <484EFC69.5080708@pobox.com> (raw)
In-Reply-To: <20080609182428.GI11300@solarflare.com>

Ben Hutchings wrote:
> Jeff,
> 
> Please add the following patch to your changes for 2.6.27.
> 
> Ben.
> 
> Ben Hutchings (1):
>   sfc: I2C adapter initialisation fixes
> 
>  drivers/net/sfc/falcon.c |   12 +++---------
>  1 files changed, 3 insertions(+), 9 deletions(-)

You're getting the email subject line a bit wrong.

If it says "[PATCH]", one expects the email to actually contain a patch...

The normal options for including comments are:

1) If it's a single patch, include meta-comments like "for 2.6.27, not 
2.6.26" after the "---" separator.  See Documentation/SubmittingPatches 
for more information.

2) If it's multiple patches, include exposition in a separate email 
numbered zero.  Example subject lines of three emails:

	[PATCH 0/2] sfc: patchset to do cool and nifty stuff

	(summarizes the patchset)

	[PATCH 1/2] sfc: add support for nifty feature bamboozle
	[PATCH 2/2] sfc: remove support for silly feature zappadoo

	(individual patches)

Regards,

	Jeff




      reply	other threads:[~2008-06-10 22:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09 18:24 [PATCH] sfc fix for 2.6.27 Ben Hutchings
2008-06-10 22:12 ` Jeff Garzik [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=484EFC69.5080708@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=bhutchings@solarflare.com \
    --cc=linux-net-drivers@solarflare.com \
    --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).