From: Shiping Ji <shiping.linux@gmail.com>
To: Scott Branden <scott.branden@broadcom.com>,
Borislav Petkov <bp@alien8.de>, James Morse <james.morse@arm.com>,
robh+dt@kernel.org, mark.rutland@arm.com
Cc: devicetree@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-edac@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
sashal@kernel.org, hangl@microsoft.com,
Lei Wang <lewan@microsoft.com>,
shji@microsoft.com, ruizhao@microsoft.com,
Yuqing Shen <yuqing.shen@broadcom.com>,
ray.jui@broadcom.com, wangglei@gmail.com
Subject: Re: [PATCH v9 2/2] EDAC: add EDAC driver for DMC520
Date: Fri, 17 Jan 2020 10:24:10 -0800 [thread overview]
Message-ID: <d05f6394-e076-6c99-965a-28444c0f24f9@gmail.com> (raw)
In-Reply-To: <aa80b8a5-5297-91c6-6410-99e43b53bd20@broadcom.com>
On 1/16/2020 4:31 PM, Scott Branden wrote:
> Hi Shiping,
>
> Here is another small change to cleanup.
>> + } else {
>> + memset(info, 0, sizeof(struct ecc_error_info));
> This should be sizeof(*info), not sizeof(struct ecc_error_info)
> for better programming to allow info to change type in the future
> without the code changing.
Yes, two occurrences will be replaced in the next patch, thanks!
--
Best regards,
Shiping Ji
prev parent reply other threads:[~2020-01-17 18:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 14:32 [PATCH v9 2/2] EDAC: add EDAC driver for DMC520 Shiping Ji
2020-01-15 21:38 ` Borislav Petkov
2020-01-15 21:49 ` Shiping Ji
2020-01-15 22:05 ` Borislav Petkov
2020-01-15 22:08 ` Shiping Ji
2020-01-17 0:18 ` Borislav Petkov
2020-01-17 18:31 ` Shiping Ji
2020-01-17 18:40 ` Scott Branden
2020-01-17 18:57 ` Borislav Petkov
2020-01-17 0:31 ` Scott Branden
2020-01-17 18:24 ` Shiping Ji [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=d05f6394-e076-6c99-965a-28444c0f24f9@gmail.com \
--to=shiping.linux@gmail.com \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=hangl@microsoft.com \
--cc=james.morse@arm.com \
--cc=lewan@microsoft.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=ray.jui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=ruizhao@microsoft.com \
--cc=sashal@kernel.org \
--cc=scott.branden@broadcom.com \
--cc=shji@microsoft.com \
--cc=wangglei@gmail.com \
--cc=yuqing.shen@broadcom.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).