netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 0/6] cxgb4: collect hardware logs via ethtool
Date: Thu, 07 Dec 2017 14:57:52 -0500 (EST)	[thread overview]
Message-ID: <20171207.145752.724969556959595708.davem@davemloft.net> (raw)
In-Reply-To: <20171207.145606.1899010205120159321.davem@davemloft.net>

From: David Miller <davem@davemloft.net>
Date: Thu, 07 Dec 2017 14:56:06 -0500 (EST)

> From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
> Date: Thu,  7 Dec 2017 14:33:36 +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
> 
> Series applied.

Actually, reverted, please fix this new build warning:

drivers/net/ethernet/chelsio/cxgb4/cudbg_lib.c: In function ‘cudbg_fill_meminfo’:
drivers/net/ethernet/chelsio/cxgb4/cudbg_lib.c:261:33: warning: ‘size’ may be used uninitialized in this function [-Wmaybe-uninitialized]
    md->limit = md->base + (size << 2) - 1;
                           ~~~~~~^~~~~

      reply	other threads:[~2017-12-07 19:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07  9:03 [PATCH net-next 0/6] cxgb4: collect hardware logs via ethtool Rahul Lakkireddy
2017-12-07  9:03 ` [PATCH net-next 1/6] cxgb4: collect on-chip memory information Rahul Lakkireddy
2017-12-07  9:03 ` [PATCH net-next 2/6] cxgb4: collect MC memory dump Rahul Lakkireddy
2017-12-07  9:03 ` [PATCH net-next 3/6] cxgb4: collect HMA " Rahul Lakkireddy
2017-12-07  9:03 ` [PATCH net-next 4/6] cxgb4: skip TX and RX payload regions in memory dumps Rahul Lakkireddy
2017-12-07  9:03 ` [PATCH net-next 5/6] cxgb4: collect egress and ingress SGE queue contexts Rahul Lakkireddy
2017-12-07  9:03 ` [PATCH net-next 6/6] cxgb4: collect PCIe configuration logs Rahul Lakkireddy
2017-12-07 19:56 ` [PATCH net-next 0/6] cxgb4: collect hardware logs via ethtool David Miller
2017-12-07 19:57   ` 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=20171207.145752.724969556959595708.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).