netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jgg@ziepe.ca
Cc: ganeshgr@chelsio.com, netdev@vger.kernel.org,
	nirranjan@chelsio.com, indranil@chelsio.com, dt@chelsio.com,
	linux-rdma@vger.kernel.org, swise@opengridcomputing.com,
	linux-crypto@vger.kernel.org, atul.gupta@chelsio.com,
	linux-scsi@vger.kernel.org, varun@chelsio.com,
	santosh@chelsio.com
Subject: Re: [PATCH net-next] cxgb4: use new fw interface to get the VIN and smt index
Date: Thu, 22 Nov 2018 10:53:49 -0800 (PST)	[thread overview]
Message-ID: <20181122.105349.1035544140286401266.davem@davemloft.net> (raw)
In-Reply-To: <20181122024624.GA28494@ziepe.ca>

From: Jason Gunthorpe <jgg@ziepe.ca>
Date: Wed, 21 Nov 2018 19:46:24 -0700

> On Wed, Nov 21, 2018 at 01:40:24PM +0530, Ganesh Goudar wrote:
>> From: Santosh Rastapur <santosh@chelsio.com>
>> 
>> If the fw supports returning VIN/VIVLD in FW_VI_CMD save it
>> in port_info structure else retrieve these from viid and save
>> them  in port_info structure. Do the same for smt_idx from
>> FW_VI_MAC_CMD
>> 
>> Signed-off-by: Santosh Rastapur <santosh@chelsio.com>
>> Signed-off-by: Ganesh Goudar <ganeshgr@chelsio.com>
>>  drivers/crypto/chelsio/chtls/chtls_cm.c         |  3 +-
>>  drivers/infiniband/hw/cxgb4/cm.c                |  6 +--
>>  drivers/net/ethernet/chelsio/cxgb4/cxgb4.h      | 12 ++++-
>>  drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c | 58 ++++++++++++-------------
>>  drivers/net/ethernet/chelsio/cxgb4/l2t.c        | 13 +++---
>>  drivers/net/ethernet/chelsio/cxgb4/t4_hw.c      | 46 ++++++++++++++++++--
>>  drivers/net/ethernet/chelsio/cxgb4/t4fw_api.h   | 20 +++++++++
>>  drivers/scsi/cxgbi/cxgb4i/cxgb4i.c              |  3 +-
>>  drivers/target/iscsi/cxgbit/cxgbit_cm.c         |  8 ++--
>>  9 files changed, 114 insertions(+), 55 deletions(-)
> 
> Applied to for-next, but please try to write better commit messages in
> future, explain what benifit your change is bringing.

The subject line indicates this is targetting my net-next tree, therefore
why did you apply it to your's?

  reply	other threads:[~2018-11-23  5:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21  8:10 [PATCH net-next] cxgb4: use new fw interface to get the VIN and smt index Ganesh Goudar
2018-11-22  2:46 ` Jason Gunthorpe
2018-11-22 18:53   ` David Miller [this message]
2018-11-22 18:58     ` Jason Gunthorpe
2018-11-23 19:11 ` 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=20181122.105349.1035544140286401266.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=atul.gupta@chelsio.com \
    --cc=dt@chelsio.com \
    --cc=ganeshgr@chelsio.com \
    --cc=indranil@chelsio.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nirranjan@chelsio.com \
    --cc=santosh@chelsio.com \
    --cc=swise@opengridcomputing.com \
    --cc=varun@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).