From: Florian Fainelli <f.fainelli@gmail.com>
To: kernel test robot <lkp@intel.com>, Ansuel Smith <ansuelsmth@gmail.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: dsa: qca8k: fix noderef.cocci warnings
Date: Wed, 9 Feb 2022 19:30:48 -0800 [thread overview]
Message-ID: <6c74b2f8-dd83-c4f2-cadd-07794a37dfac@gmail.com> (raw)
In-Reply-To: <20220209221304.GA17529@d2214a582157>
On 2/9/2022 2:13 PM, kernel test robot wrote:
> From: kernel test robot <lkp@intel.com>
>
> drivers/net/dsa/qca8k.c:422:37-43: ERROR: application of sizeof to pointer
>
> sizeof when applied to a pointer typed expression gives the size of
> the pointer
>
> Generated by: scripts/coccinelle/misc/noderef.cocci
>
> Fixes: 90386223f44e ("net: dsa: qca8k: add support for larger read/write size with mgmt Ethernet")
> CC: Ansuel Smith <ansuelsmth@gmail.com>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: kernel test robot <lkp@intel.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2022-02-10 3:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 22:18 [linux-next:master 2955/4656] drivers/net/dsa/qca8k.c:422:37-43: ERROR: application of sizeof to pointer kernel test robot
2022-02-09 22:13 ` [PATCH] net: dsa: qca8k: fix noderef.cocci warnings kernel test robot
2022-02-10 3:30 ` Florian Fainelli [this message]
2022-02-10 18:59 ` Jakub Kicinski
2022-02-11 6:36 ` [kbuild-all] " Chen, Rong A
-- strict thread matches above, loose matches on Subject: below --
2022-02-10 12:55 [linux-next:master 2956/4901] drivers/net/dsa/qca8k.c:422:37-43: ERROR: application of sizeof to pointer kernel test robot
2022-02-10 12:46 ` [PATCH] net: dsa: qca8k: fix noderef.cocci warnings kernel test robot
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=6c74b2f8-dd83-c4f2-cadd-07794a37dfac@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.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).