netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: hariprasad@chelsio.com
Cc: netdev@vger.kernel.org, leedom@chelsio.com, nirranjan@chelsio.com
Subject: Re: [PATCH net] cxgb4: Changes for new firmware 1.14.4.0
Date: Wed, 09 Sep 2015 12:33:59 -0700 (PDT)	[thread overview]
Message-ID: <20150909.123359.137728939050408728.davem@davemloft.net> (raw)
In-Reply-To: <1441627850-5610-1-git-send-email-hariprasad@chelsio.com>

From: Hariprasad Shenai <hariprasad@chelsio.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@chelsio.com>

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

commit a69265e9f65a6747c27b01b4030ad85d71aa11ba
Author: Hariprasad Shenai <hariprasad@chelsio.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@chelsio.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

  reply	other threads:[~2015-09-09 19:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07 12:10 [PATCH net] cxgb4: Changes for new firmware 1.14.4.0 Hariprasad Shenai
2015-09-09 19:33 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-09-10  4:25 [PATCH net] cxgb4: changes " Hariprasad Shenai
2015-09-10  4:30 ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150909.123359.137728939050408728.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=hariprasad@chelsio.com \
    --cc=leedom@chelsio.com \
    --cc=netdev@vger.kernel.org \
    --cc=nirranjan@chelsio.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).