netdev - Re: [PATCH] ethernet/arc/arc_emac: drop redundant mac address check

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: <20131029091028.GA18147@w500.lan>
Date:	Tue, 29 Oct 2013 10:10:28 +0100
From:	Luka Perkov <luka@...nwrt.org>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, abrodkin@...opsys.com
Subject: Re: [PATCH] ethernet/arc/arc_emac: drop redundant mac address check

Hi David,

On Mon, Oct 28, 2013 at 11:48:42PM -0400, David Miller wrote:
> I've seen you use three inconsistent Subject prefixes here, pick a scheme
> and stick to it please!
> 
> First patch was:
> 
> netdev: ${driver_name}:
> 
> Second patch was:
> 
> net: ${driver_name}:
> 
> Third patch was:
> 
> patch/to/driver/directory:

True. I have sent it that way because I've followed the commit
schematics of each driver individually.

> This is really not acceptable.  Just using "${driver_name}: " is good
> enough.

It's not a problem to resend them... But I'm wondering should this be
squashed into one patch?

Luka
--
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