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  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, 17 Jul 2014 09:36:40 +0200
From:	Tom Gundersen <>
To:	Veaceslav Falico <>
Cc:	David Miller <>,
	netdev <>,
	LKML <>
Subject: Re: [PATCH v8] net: set name assign type for names assigned using a
 static string

On Thu, Jul 17, 2014 at 9:26 AM, Veaceslav Falico <> wrote:
> On Thu, Jul 17, 2014 at 09:17:07AM +0200, Tom Gundersen wrote:
>> On Thu, Jul 17, 2014 at 8:56 AM, David Miller <> wrote:
>>> Tom, even if the patches are sort of independent, they logically
>>> belong together.
>>> So please number them, and provide an appropriate "[PATCH 0/N] ..."
>>> cover letter.
>>> Please resubmit these patches with that done properly, thank you.
>> Ok. Will do.
> Also, it would be really nice if you could send patches as
> Doc/net/netdev-FAQ.txt suggests, as lots of us have scripts that parse the
> subject to find out which tree to apply/test the patches.
> It's also easier than using git notes edit/git send-email --notes :).
> Q: How do I indicate which tree (net vs. net-next) my patch should be in?
> A: Firstly, think whether you have a bug fix or new "next-like" content.
>   Then once decided, assuming that you use git, use the prefix flag, i.e.
>        git format-patch --subject-prefix='PATCH net-next' start..finish
>   Use "net" instead of "net-next" (always lower case) in the above for
>   bug-fix net content.  If you don't use git, then note the only magic in
>   the above is just the subject text of the outgoing e-mail, and you can
>   manually change it yourself with whatever MUA you are comfortable with.

Ok. Will do.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists