linux-kernel - Re: [PATCH v2] 3c59x: fix bad split of cpu_to_le32(pci_map

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20140929.160813.1739128124571074828.davem@davemloft.net>
Date:	Mon, 29 Sep 2014 16:08:13 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	sylvain.hitier@...il.com
Cc:	nhorman@...driver.com, linux-kernel@...r.kernel.org, mroos@...ux.ee
Subject: Re: [PATCH v2] 3c59x: fix bad split of
 cpu_to_le32(pci_map_single())

From: Sylvain 'ythier' Hitier <sylvain.hitier@...il.com>
Date: Mon, 29 Sep 2014 19:45:12 +0000

> When: 2014-09-29_1@...37-48 -0400
> Who:  David Miller
> What:
>> Can someone please clean this up and submit it properly?
> 
> I'm willing to do it, but...
> could you elaborate on "clean up" and "properly"?
> 
> Would it be OK for me re-sending my part as v3 including Neil's ack?
> Or are you expecting a unique patch combining Neil's changes and mine?

You should not submit patches as a reply to a discussion, it must be
done as a fresh mailing list posting.

The posting must also be properly formed, in that "Subject: " should
be of the form "[PATCH vx] ${subsystem}: Description."  and the mail
message body must be the commit message with appropriate signoffs
and ACKs, then the patch comes next.

This is fully described, in detail, in Documentation/SubmittingPatches
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/