linux-kernel - Re: [PATCH v2] scsi: be2iscsi: Use kasprintf

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: <yq17ev772jc.fsf@oracle.com>
Date:   Fri, 03 Nov 2017 12:25:11 -0400
From:   "Martin K. Petersen" <martin.petersen@...cle.com>
To:     Himanshu Jha <himanshujha199640@...il.com>
Cc:     "Martin K. Petersen" <martin.petersen@...cle.com>,
        jejb@...ux.vnet.ibm.com, linux-scsi@...r.kernel.org,
        linux-kernel@...r.kernel.org, subbu.seetharaman@...adcom.com,
        ketan.mukadam@...adcom.com, jitendra.bhivare@...adcom.com
Subject: Re: [PATCH v2] scsi: be2iscsi: Use kasprintf


Himanshu,

>> It is not. It needs a review/ack from the driver maintainers.
>
> What about Kyle Fortin's review ?

Kyle's review is fine. But when a driver is actively maintained, like
be2iscsi is, I always give ack/nack rights to the relevant maintainers.
In this case that's Jitendra.

-- 
Martin K. Petersen	Oracle Linux Engineering