From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
netdev <netdev@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 2/3] ravb: fix warning about memcpy length
Date: Mon, 16 Jul 2018 17:45:32 +0200 [thread overview]
Message-ID: <CAMuHMdUpWKwzxgYfaqjuW-dbS06d0VedsDi1zspbYQtvVo9_ag@mail.gmail.com> (raw)
In-Reply-To: <20180716121927.21918-3-niklas.soderlund+renesas@ragnatech.se>
On Mon, Jul 16, 2018 at 2:20 PM Niklas Söderlund
<niklas.soderlund+renesas@ragnatech.se> wrote:
> This fixes sparse warning:
>
> ravb_main.c:1257 ravb_get_strings() error: memcpy() '*ravb_gstrings_stats' too small (32 vs 960)
>
> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2018-07-16 16:13 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 [this message]
2018-07-16 19:18 ` Sergei Shtylyov
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=CAMuHMdUpWKwzxgYfaqjuW-dbS06d0VedsDi1zspbYQtvVo9_ag@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=sergei.shtylyov@cogentembedded.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).