From: David Miller <davem@davemloft.net>
To: rahul.lakkireddy@chelsio.com
Cc: netdev@vger.kernel.org, ganeshgr@chelsio.com,
nirranjan@chelsio.com, indranil@chelsio.com
Subject: Re: [PATCH net-next v2 0/6] cxgb4: collect hardware logs via ethtool
Date: Fri, 08 Dec 2017 14:34:35 -0500 (EST) [thread overview]
Message-ID: <20171208.143435.494133025503583128.davem@davemloft.net> (raw)
In-Reply-To: <cover.1512705841.git.rahul.lakkireddy@chelsio.com>
From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Date: Fri, 8 Dec 2017 09:48:35 +0530
> Collect more hardware logs via ethtool --get-dump facility.
>
> Patch 1 collects on-chip memory layout information.
>
> Patch 2 collects on-chip MC memory dumps.
>
> Patch 3 collects HMA memory dump.
>
> Patch 4 evaluates and skips TX and RX payload regions in memory dumps.
>
> Patch 5 collects egress and ingress SGE queue contexts.
>
> Patch 6 collects PCIe configuration logs
...
> ---
> v2:
> - Fix uninitialized variable "size" build warning in Patch 1.
That looks better, series applied, thanks.
prev parent reply other threads:[~2017-12-08 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 4:18 [PATCH net-next v2 0/6] cxgb4: collect hardware logs via ethtool Rahul Lakkireddy
2017-12-08 4:18 ` [PATCH net-next v2 1/6] cxgb4: collect on-chip memory information Rahul Lakkireddy
2017-12-08 4:18 ` [PATCH net-next v2 2/6] cxgb4: collect MC memory dump Rahul Lakkireddy
2017-12-08 4:18 ` [PATCH net-next v2 3/6] cxgb4: collect HMA " Rahul Lakkireddy
2017-12-08 4:18 ` [PATCH net-next v2 4/6] cxgb4: skip TX and RX payload regions in memory dumps Rahul Lakkireddy
2017-12-08 4:18 ` [PATCH net-next v2 5/6] cxgb4: collect egress and ingress SGE queue contexts Rahul Lakkireddy
2017-12-08 4:18 ` [PATCH net-next v2 6/6] cxgb4: collect PCIe configuration logs Rahul Lakkireddy
2017-12-08 19:34 ` 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=20171208.143435.494133025503583128.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ganeshgr@chelsio.com \
--cc=indranil@chelsio.com \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.com \
--cc=rahul.lakkireddy@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).