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]
Date:	Thu, 14 Jan 2016 19:16:25 +0100
From:	Andrew Lunn <andrew@...n.ch>
To:	Rene Rebe <rene@...ctcode.com>
Cc:	netdev@...r.kernel.org, davem@...emloft.net
Subject: Re: [PATCH] r8152 add Microsoft Dock IDs

On Thu, Jan 14, 2016 at 06:46:26PM +0100, Rene Rebe wrote:
> Hi David,
> (my appologies for wasting your time with this noise)
> 
> rebased against your netdev git, and sent with Mew:

Hi Rene

So, slowly getting better. However, go read
Documentation/SubmittingPatches

Read the bit about the "---" marker.

netdev also has a few additional rules, which are not documented in
SubmittingPatches.

In the subject line, you should include which tree this patch is
supposed to be applied to. In this case, it is net-next. So you
subject line should be

Subject: [PATCH net-next] r8152 add Microsoft Dock IDs

and obviously, your patch needs to cleanly apply to net-next, not some
other random tree.

The other rule which is relevant at the moment, is that net-next is
closed, because the merge window is open. So please wait about 12 days
for net-next to reopen. David will probably send an email saying he is
ready to accept new patches.

      Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ