I spent last night cleaning up patchwork. Not entirely done yet but
getting down to a manageable size:

        https://patchwork.kernel.org/project/linux-scsi/list/


These are 4.4 fixes that I'd like to get some more reviews for:

        scsi_debug: fix prevent_allow+verify regressions
        https://patchwork.kernel.org/patch/7676711/

        Fix a bdi reregistration race, v2
        https://patchwork.kernel.org/patch/7671671/

        Revert "scsi: Fix a bdi reregistration race"
        https://patchwork.kernel.org/patch/7671661/

        [2/2] Fix a memory leak in scsi_host_dev_release()
        https://patchwork.kernel.org/patch/7671391/

        [1/2] scsi_transport_fc: Introduce scsi_host_{get,put}()
        https://patchwork.kernel.org/patch/7671381/

        [3/3] MAINTAINERS: Add myself as co-maintainer of the SCSI subsystem.
        https://patchwork.kernel.org/patch/7614881/

        [2/3] block/sd: Fix device-imposed transfer length limits
        https://patchwork.kernel.org/patch/7614871/

        [1/3] sd: Make discard granularity match logical block size when LBPRZ=1
        https://patchwork.kernel.org/patch/7614861/


And for 4.5 the following ones are low-hanging fruit.

        scsi: hisi_sas: remove dependency on of_irq_count
        https://patchwork.kernel.org/patch/7656691/

        scsi: use sector_div instead of do_div
        https://patchwork.kernel.org/patch/7669841/

        mvsas: add SGPIO support to Marvell 94xx
        https://patchwork.kernel.org/patch/7610411/

        aacraid: aac_release_resources() can be static
        https://patchwork.kernel.org/patch/7588331/

I staged the reviewed portion of Finn's ncr5380 series last week but it
looks like there is some issues to be worked out. So I'll let that
simmer in a different branch for now.

I will take a look at the ALUA series today. And then there's the
mountain of UFS related patch series...

-- 
Martin K. Petersen      Oracle Linux Engineering
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to