From: David Miller <davem@davemloft.net>
To: hariprasad@chelsio.com
Cc: netdev@vger.kernel.org, leedom@chelsio.com, nirranjan@chelsio.com
Subject: Re: [PATCHv3 net-next 0/4] cxgb4: Trivial fixes for cxgb4
Date: Mon, 05 Oct 2015 03:51:23 -0700 (PDT) [thread overview]
Message-ID: <20151005.035123.617026778484482371.davem@davemloft.net> (raw)
In-Reply-To: <1443687528-25836-1-git-send-email-hariprasad@chelsio.com>
From: Hariprasad Shenai <hariprasad@chelsio.com>
Date: Thu, 1 Oct 2015 13:48:44 +0530
> Fixes the following issues
> Don't read non existent T4/T5/T6 adapter registers for ethtool dump.
> For T4, dont read mailbox control registers. Adds new devlog faility and
> report correct link speed for unsupported ones.
>
> This patch series has been created against net-next tree and includes
> patches on cxgb4 driver.
>
> We have included all the maintainers of respective drivers. Kindly review
> the change and let us know in case of any review comments.
>
> Thanks
>
> V3: Add an "<unread>" entry to char *owner[] array so the index of "4"
> makes sense, based on review comment by Casey Leedom <leedom@chelsio.com>
> V2: Fix coding style for Patch2/4 ("cxgb4: For T4, don't read the Firmware
> Mailbox Control register") based on review comment by Sergei Shtylyov
Series applied, thanks.
prev parent reply other threads:[~2015-10-05 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 8:18 [PATCHv3 net-next 0/4] cxgb4: Trivial fixes for cxgb4 Hariprasad Shenai
2015-10-01 8:18 ` [PATCHv3 net-next 1/4] cxgb4 : Update T4/T5/T6 register ranges Hariprasad Shenai
2015-10-01 8:18 ` [PATCHv3 net-next 2/4] cxgb4: For T4, don't read the Firmware Mailbox Control register Hariprasad Shenai
2015-10-01 8:18 ` [PATCHv3 net-next 3/4] cxgb4: Adds a new Device Log Facility FW_DEVLOG_FACILITY_CF Hariprasad Shenai
2015-10-01 8:18 ` [PATCHv3 net-next 4/4] cxgb4: Report correct link speed for unsupported ones Hariprasad Shenai
2015-10-05 10:51 ` David Miller [this message]
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=20151005.035123.617026778484482371.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).