netdev - Re: [PATCH] sfc fix for 2.6.27

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <484EFC69.5080708@pobox.com>
Date:	Tue, 10 Jun 2008 18:12:57 -0400
From:	Jeff Garzik <jgarzik@...ox.com>
To:	Ben Hutchings <bhutchings@...arflare.com>
CC:	netdev@...r.kernel.org, linux-net-drivers@...arflare.com
Subject: Re: [PATCH] sfc fix for 2.6.27

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

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html