From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
netdev@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 2/3] ravb: fix warning about memcpy length
Date: Mon, 16 Jul 2018 22:18:13 +0300 [thread overview]
Message-ID: <b1dd6076-7c20-9b11-47c5-dfa847f89ccf@cogentembedded.com> (raw)
In-Reply-To: <20180716121927.21918-3-niklas.soderlund+renesas@ragnatech.se>
On 07/16/2018 03:19 PM, Niklas Söderlund wrote:
> This fixes sparse warning:
>
> ravb_main.c:1257 ravb_get_strings() error: memcpy() '*ravb_gstrings_stats' too small (32 vs 960)
It's good that's not a real bug! :-)
> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
[...]
Acked-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
MBR, Sergei
next prev parent reply other threads:[~2018-07-16 19:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 12:19 [PATCH 0/3] ravb: small sparse fixes Niklas Söderlund
2018-07-16 12:19 ` [PATCH 1/3] ravb: fix shadowing of symbol 'stats' in ravb_get_ethtool_stats() Niklas Söderlund
2018-07-16 15:38 ` Geert Uytterhoeven
2018-07-16 19:08 ` Sergei Shtylyov
2018-07-16 12:19 ` [PATCH 2/3] ravb: fix warning about memcpy length Niklas Söderlund
2018-07-16 15:45 ` Geert Uytterhoeven
2018-07-16 19:18 ` Sergei Shtylyov [this message]
2018-07-16 12:19 ` [PATCH 3/3] ravb: fix byte order for TX descriptor tag field lower bits Niklas Söderlund
2018-07-16 15:47 ` Geert Uytterhoeven
2018-07-16 19:52 ` Sergei Shtylyov
2018-07-16 20:22 ` Sergei Shtylyov
2018-07-16 20:32 ` Geert Uytterhoeven
2018-07-18 5:22 ` [PATCH 0/3] ravb: small sparse fixes David Miller
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=b1dd6076-7c20-9b11-47c5-dfa847f89ccf@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
/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).