linux-kernel - Re: [patch set 4.19.6] BFS updates

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: <20181203102631.GA18219@kroah.com>
Date:   Mon, 3 Dec 2018 11:26:31 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Tigran Aivazian <aivazian.tigran@...il.com>
Cc:     torvalds@...ux-foundation.org, LKML <linux-kernel@...r.kernel.org>,
        stable@...r.kernel.org
Subject: Re: [patch set 4.19.6] BFS updates

On Mon, Dec 03, 2018 at 09:55:23AM +0000, Tigran Aivazian wrote:
> Re-sending the patches with the "Cc: stable@...r.kernel.org" included
> in the sign-off area, as per Option 1 of the rules Greg referred me
> to. I hope that now I have done everything by the rules.

As you want to replace an existing patch in linux-next that is in
Andrew's trees, you need to cc: him :)

Also, you need to send each patch as an individual email, like
Documentation/SubmittingPatches says to do.

This shouldn't be any different from submitting any other patch.

thanks,

greg k-h