From: Timur Tabi <timur@codeaurora.org>
To: Rami Rosen <roszenrami@gmail.com>
Cc: Netdev <netdev@vger.kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
sdharia@codeaurora.org, shankerd@codeaurora.org,
vikrams@codeaurora.org, cov@codeaurora.org,
gavidov@codeaurora.org, robh+dt@kernel.org, andrew@lunn.ch,
bjorn.andersson@linaro.org, mlangsdo@redhat.com, jcm@redhat.com,
agross@codeaurora.org, David Miller <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
LinoSanfilippo@gmx.de
Subject: Re: [PATCH] [v9] net: emac: emac gigabit ethernet controller driver
Date: Wed, 31 Aug 2016 13:57:56 -0500 [thread overview]
Message-ID: <57C728B4.7070303@codeaurora.org> (raw)
In-Reply-To: <57C1FB42.104@codeaurora.org>
Timur Tabi wrote:
>
>> Seems that there are several unused members in the emac_stats struct:
>>
>>> +struct emac_stats {
>> ...
>> ...
>> Both rx_bcast_byte_cnt and rx_mcast_byte_cnt are not used anywhere/
>>> + u64 rx_bcast_byte_cnt; /* broadcast packets byte count
>>> (without FCS) */
>>> + u64 rx_mcast_byte_cnt; /* multicast packets byte count
>>> (without FCS) */
>> ...
>> rx_err_addr is not used
>>> + u64 rx_err_addr; /* packets dropped due to address
>>> filtering */
>
> I'll go through the structure and remove the unused fields.
It turns out I cannot actually strip out those "unused" fields. They
are all indirectly used in emac_get_stats64:
u64 *stats_itr = &adpt->stats.rx_ok;
while (addr <= REG_MAC_RX_STATUS_END) {
val = readl_relaxed(adpt->base + addr);
*stats_itr += val;
stats_itr++;
addr += sizeof(u32);
}
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc. Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2016-08-31 18:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 21:39 [PATCH] [v9] net: emac: emac gigabit ethernet controller driver Timur Tabi
2016-08-27 4:29 ` David Miller
2016-08-27 12:26 ` Timur Tabi
2016-08-27 17:58 ` Florian Fainelli
2016-08-28 4:50 ` David Miller
2016-08-27 20:26 ` Rami Rosen
[not found] ` <CAKoUAr=Z56VxzW=zHu7r9ossdXHQ6xpeYdR5jwhv38zkV_eKFQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-08-27 20:42 ` Timur Tabi
2016-08-31 18:57 ` Timur Tabi [this message]
2016-08-31 19:15 ` Florian Fainelli
[not found] ` <60d13549-f9ea-694b-1030-0c610e0d9722-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-08-31 19:19 ` Timur Tabi
[not found] ` <1472161143-26417-1-git-send-email-timur-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-08-31 15:00 ` Rob Herring
2016-08-31 15:11 ` Timur Tabi
2016-08-31 20:46 ` Rob Herring
[not found] ` <CAL_Jsq+BtwBtB7Vd8HB+vhucfUmn_0bxRRXmyO13GoCM82LgFg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-08-31 21:00 ` Timur Tabi
[not found] ` <57C74562.3050203-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-08-31 21:16 ` Andrew Lunn
2016-09-01 22:49 ` Rob Herring
2016-08-31 15:24 ` Andrew Lunn
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=57C728B4.7070303@codeaurora.org \
--to=timur@codeaurora.org \
--cc=LinoSanfilippo@gmx.de \
--cc=agross@codeaurora.org \
--cc=andrew@lunn.ch \
--cc=bjorn.andersson@linaro.org \
--cc=cov@codeaurora.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gavidov@codeaurora.org \
--cc=jcm@redhat.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mlangsdo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=roszenrami@gmail.com \
--cc=sdharia@codeaurora.org \
--cc=shankerd@codeaurora.org \
--cc=vikrams@codeaurora.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).