linux-kernel - Re: [PATCH 1/2] fixup! net/macb: Adding comments to various #defs to make interpretation easier

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]

Date:	Wed, 14 Jan 2015 16:52:20 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	xander.huff@...com
Cc:	nicolas.ferre@...el.com, netdev@...r.kernel.org,
	jaeden.amero@...com, rich.tollerton@...com, ben.shelton@...com,
	brad.mouring@...com, linux-kernel@...r.kernel.org,
	cyrille.pitchen@...el.com
Subject: Re: [PATCH 1/2] fixup! net/macb: Adding comments to various #defs
 to make interpretation easier

From: Xander Huff <xander.huff@...com>
Date: Wed, 14 Jan 2015 15:18:34 -0600

> On 1/14/2015 3:09 PM, David Miller wrote:
>>
>> As I mentioned, this won't do.
>>
>> I've already applied your original patches to net-next, therefore you
>> will
>> have to submit fixups relative to that.
>>
> These fixup commits are relative to an updated net-next, specifically
> "237de6e Merge branch 'hip04'".
> 
> Do you need them relative to (what I'm seeing is the latest) "2733135
> Merge branch 'vxlan_rco'"?

Why don't you make your subject lines and commit messages just say what
they are doing, rather than just saying "fix this other change"?
--
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/