netdev - Re: [PATCH 0/4] pch_gbe fixes and enhancements

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20131129.164329.1281195296685567024.davem@davemloft.net>
Date:	Fri, 29 Nov 2013 16:43:29 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	puzman@...il.com
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] pch_gbe fixes and enhancements

From: Ondrej Puzman <puzman@...il.com>
Date: Thu, 28 Nov 2013 10:44:38 +0100

> Hi,
> I'm sending the pch_gbe patch set again per David Miller's request.
> Now the patches should be correctly numbered.
> 
> The patches fixes problems I found on our industrial computer with
> Intel Atom E680T CPU and EG20T chipset.

Some of these patches are adding new features, which is not appropriate
to submit until the net-next tree is open, which it is not.

It is also not appropriate to mix bug fixes with new feature additions.

Bug fixes should be separated out and submitted targetting the
'net' tree, and then new features should be submitted targetting the
'net-next' tree but only when it is open for new changes.
--
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