netdev - Re: [PATCH net] cxgb4: Changes for new firmware 1.14.4.0

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: <20150909.123359.137728939050408728.davem@davemloft.net>
Date:	Wed, 09 Sep 2015 12:33:59 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	hariprasad@...lsio.com
Cc:	netdev@...r.kernel.org, leedom@...lsio.com, nirranjan@...lsio.com
Subject: Re: [PATCH net] cxgb4: Changes for new firmware 1.14.4.0

From: Hariprasad Shenai <hariprasad@...lsio.com>
Date: Mon,  7 Sep 2015 17:40:50 +0530

> Incorporate fw_ldst_cmd structure change for new firmware and also
> update version string for the same
> 
> Signed-off-by: Hariprasad Shenai <hariprasad@...lsio.com>

This doesn't apply cleanly at all, please respin as it has to
take into account commit:

commit a69265e9f65a6747c27b01b4030ad85d71aa11ba
Author: Hariprasad Shenai <hariprasad@...lsio.com>
Date:   Fri Aug 28 11:17:12 2015 +0530

    cxgb4: Force uninitialized state if FW in adapter is unsupported
    
    Forcing uninitialized state allows us to upgrade and reinitialize
    the adapter.
    
        FW_VERSION_T4 = 1.4.0.0
        FW_VERSION_T5 = 0.0.0.0
        FW_VERSION_T6 = 0.0.0.0
    At this point driver supports above and greater than above version.
    
    If FW in adapter < min FW_VERSION driver supports tries to upgrade the FW
    If FW in adapter >= FW_VERSION driver supports then it follows normal path
    
    Signed-off-by: Hariprasad Shenai <hariprasad@...lsio.com>
    Signed-off-by: David S. Miller <davem@...emloft.net>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html