linux-kernel - Re: [PATCH] aic7xxx: fix firmware build with O=path

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: <yq1wp75b3n6.fsf@oracle.com>
Date:   Tue, 18 Jul 2017 21:45:49 -0400
From:   "Martin K. Petersen" <martin.petersen@...cle.com>
To:     Jakub Kicinski <jakub.kicinski@...ronome.com>
Cc:     Hannes Reinecke <hare@...e.com>,
        "James E.J. Bottomley" <jejb@...ux.vnet.ibm.com>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
        oss-drivers@...ronome.com
Subject: Re: [PATCH] aic7xxx: fix firmware build with O=path


Jakub,

> I just noticed this patch got marked as "Deferred, archived" in
> patchwork.  I'm not entirely sure by whom and why?  Could someone
> explain what is the issue?  I would really appreciate if we could 
> merge this patch and have this driver not break builds randomly...

It's an indication that the patch sat around without any reviews for way
too long.

People generally don't go chasing around in their mail archives for
several week old patches to review. The best thing to do for patches I
mark as deferred is to resubmit them so they get back on people's radar.

-- 
Martin K. Petersen	Oracle Linux Engineering