linux-kernel - Re: [PATCH -next] platform/chrome: Fix off-by-one error in wilco

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190221070704.GD1711@kadam>
Date:   Thu, 21 Feb 2019 21:31:54 +0300
From:   Dan Carpenter <dan.carpenter@...cle.com>
To:     Nick Crews <ncrews@...omium.org>
Cc:     Enric Balletbo i Serra <enric.balletbo@...labora.com>,
        Benson Leung <bleung@...omium.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        kernel-janitors@...r.kernel.org,
        Duncan Laurie <dlaurie@...omium.org>
Subject: Re: [PATCH -next] platform/chrome: Fix off-by-one error in
 wilco_ec/debugfs.c

On Wed, Feb 20, 2019 at 03:15:18PM -0700, Nick Crews wrote:
> Fixing something after it's already in the tree was a new
> process for me, so I tried to copy other people's examples. Please
> let me know if there's anything else I should do something different
> next time.

I seldom mention how much I like Reported-by tags because it makes me
seem needy...  Also in this case it doesn't matter because it's going to
get folded into the original patch so it's going to be lost anyway.  But
since you're asking process questions, the Reported-by cookie is nice.

Reported-by: Dan Carpenter <dan.carpenter@...cle.com>

regards,
dan carpenter