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  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:   Sun, 30 Aug 2020 19:18:20 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     deesin@...eaurora.org
Cc:     bjorn.andersson@...aro.org, clew@...eaurora.org,
        mathieu.poirier@...aro.org, linux-arm-msm@...r.kernel.org,
        linux-remoteproc@...r.kernel.org, linux-kernel@...r.kernel.org,
        kuba@...nel.org, manivannan.sadhasivam@...aro.org,
        cjhuang@...eaurora.org, necip@...gle.com, netdev@...r.kernel.org
Subject: Re: [PATCH V1 1/4] net: qrtr: Do not send packets before hello
 negotiation


A proper patch series must provide a header "[PATCH 0/N ..." posting which
explains what the patch series does, at a high level, how it does it, and
why it does it that way.

You must also explicitly state the target GIT tree your changes are for
in the subject line, f.e. "[PATCH net-next M/N] ..."

I'm sorry I have to be strict about this but it is very important for
reviewers, and anyone looking at these changes in the future, to have
this summary information.

Thank you.

Powered by blists - more mailing lists