From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Naresh Kumar Inna <naresh@chelsio.com>
Cc: linux-scsi@vger.kernel.org, dm@chelsio.com, leedom@chelsio.com,
netdev@vger.kernel.org, chethan@chelsio.com
Subject: Re: [v6 PATCH 1/8] cxgb4/cxgb4vf: Chelsio FCoE offload driver submission (common header updates).
Date: Tue, 13 Nov 2012 18:26:48 -0800 [thread overview]
Message-ID: <1352860008.28921.2.camel@dabdike> (raw)
In-Reply-To: <1351158621-32222-2-git-send-email-naresh@chelsio.com>
On Thu, 2012-10-25 at 15:20 +0530, Naresh Kumar Inna wrote:
> This patch contains updates to firmware/hardware header files shared
> between csiostor and cxgb4/cxgb4vf, and the resulting changes to the
> cxgb4/cxgb4vf source files.
>
> Signed-off-by: Naresh Kumar Inna <naresh@chelsio.com>
> ---
> drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c | 8 ++--
> drivers/net/ethernet/chelsio/cxgb4/sge.c | 6 ++--
> drivers/net/ethernet/chelsio/cxgb4/t4_hw.c | 20 +++++-----
> drivers/net/ethernet/chelsio/cxgb4/t4_msg.h | 1 +
> drivers/net/ethernet/chelsio/cxgb4/t4_regs.h | 36 +++++++++++++++++++-
> drivers/net/ethernet/chelsio/cxgb4/t4fw_api.h | 41 ++++++++++++++++++++---
> drivers/net/ethernet/chelsio/cxgb4vf/sge.c | 8 ++--
> 7 files changed, 92 insertions(+), 28 deletions(-)
This still doesn't compile:
drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c: In function ‘adap_init0’:
drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c:3932:10: error: ‘struct fw_caps_config_cmd’ has no member named ‘retval_len16’
make[5]: *** [drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.o] Error 1
James
next prev parent reply other threads:[~2012-11-14 7:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 9:50 [v6 PATCH 0/8] csiostor: Chelsio FCoE offload driver submission Naresh Kumar Inna
2012-10-25 9:50 ` [v6 PATCH 1/8] cxgb4/cxgb4vf: Chelsio FCoE offload driver submission (common header updates) Naresh Kumar Inna
2012-11-14 2:26 ` James Bottomley [this message]
2012-11-15 11:32 ` Naresh Kumar Inna
2012-10-25 9:50 ` [v6 PATCH 2/8] csiostor: Chelsio FCoE offload driver submission (headers part 1) Naresh Kumar Inna
2012-10-25 9:50 ` [v6 PATCH 3/8] csiostor: Chelsio FCoE offload driver submission (headers part 2) Naresh Kumar Inna
2012-10-25 9:50 ` [v6 PATCH 4/8] csiostor: Chelsio FCoE offload driver submission (sources part 1) Naresh Kumar Inna
2012-10-25 9:50 ` [v6 PATCH 5/8] csiostor: Chelsio FCoE offload driver submission (sources part 2) Naresh Kumar Inna
2012-10-25 9:50 ` [v6 PATCH 6/8] csiostor: Chelsio FCoE offload driver submission (sources part 3) Naresh Kumar Inna
2012-10-25 9:50 ` [v6 PATCH 7/8] csiostor: Chelsio FCoE offload driver submission (sources part 4) Naresh Kumar Inna
2012-10-25 9:50 ` [v6 PATCH 8/8] csiostor: Chelsio FCoE offload driver submission (sources part 5) Naresh Kumar Inna
2012-11-02 7:23 ` [v6 PATCH 0/8] csiostor: Chelsio FCoE offload driver submission Naresh Kumar Inna
-- strict thread matches above, loose matches on Subject: below --
2012-11-15 17:11 Naresh Kumar Inna
2012-11-15 17:11 ` [v6 PATCH 1/8] cxgb4/cxgb4vf: Chelsio FCoE offload driver submission (common header updates) Naresh Kumar Inna
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=1352860008.28921.2.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=chethan@chelsio.com \
--cc=dm@chelsio.com \
--cc=leedom@chelsio.com \
--cc=linux-scsi@vger.kernel.org \
--cc=naresh@chelsio.com \
--cc=netdev@vger.kernel.org \
/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).