From: "Shenhar, Talel" <talel@amazon.com>
To: Borislav Petkov <bp@alien8.de>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
talel@amazon.com, hhhawa@amazon.com, gregkh@linuxfoundation.org,
eitan@amazon.com, jonnyc@amazon.com, hanochu@amazon.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
james.morse@arm.com, catalin.marinas@arm.com, ronenk@amazon.com,
mchehab@kernel.org, will@kernel.org, davem@davemloft.net,
linux-arm-kernel@lists.infradead.org, linux-edac@vger.kernel.org
Subject: Re: [PATCH v9 2/2] EDAC: al-mc-edac: Introduce Amazon's Annapurna Labs Memory Controller EDAC
Date: Sun, 16 Aug 2020 12:17:31 +0300 [thread overview]
Message-ID: <5d516c64-ecd8-6f36-5f95-6708fe0f3fd5@amazon.com> (raw)
In-Reply-To: <20200815183358.GE25814@zn.tnic>
On 8/15/2020 9:33 PM, Borislav Petkov wrote:
> On Tue, Jul 28, 2020 at 12:51:55PM +0300, Talel Shenhar wrote:
>> +static void al_mc_edac_check(struct mem_ctl_info *mci)
>> +{
>> + struct al_mc_edac *al_mc = mci->pvt_info;
>> +
>> + if (al_mc->irq_ue <= 0)
>> + handle_ue(mci);
>> +
>> + if (al_mc->irq_ce <= 0)
>> + handle_ce(mci);
>> +}
>> +
>> +static irqreturn_t al_mc_edac_irq_handler_ue(int irq, void *info)
>> +{
>> + struct platform_device *pdev = info;
>> + struct mem_ctl_info *mci = platform_get_drvdata(pdev);
>> +
>> + if (handle_ue(mci))
>> + return IRQ_HANDLED;
>> + return IRQ_NONE;
>> +}
>> +
>> +static irqreturn_t al_mc_edac_irq_handler_ce(int irq, void *info)
>> +{
>> + struct platform_device *pdev = info;
>> + struct mem_ctl_info *mci = platform_get_drvdata(pdev);
>> +
>> + if (handle_ce(mci))
>> + return IRQ_HANDLED;
>> + return IRQ_NONE;
>> +}
>> +
>> +static enum scrub_type al_mc_edac_get_scrub_mode(void __iomem *mmio_base)
>> +{
>> + u32 ecccfg0;
>> +
>> + ecccfg0 = readl(mmio_base + AL_MC_ECC_CFG);
>> +
>> + if (FIELD_GET(AL_MC_ECC_CFG_SCRUB_DISABLED, ecccfg0))
>> + return SCRUB_NONE;
>> + else
>> + return SCRUB_HW_SRC;
>> +}
>> +
>> +static void devm_al_mc_edac_free(void *data)
>> +{
>> + edac_mc_free(data);
>> +}
>> +
>> +static void devm_al_mc_edac_del(void *data)
>> +{
>> + edac_mc_del_mc(data);
>> +}
> From a previous review:
>
> I said:
>
>> Drop the "al_mc_edac_" prefix from most of the static functions. You can
>> leave it in the probe function or the IRQ handler so that it is visible
>> in stack traces but all those small functions don't need that prefix.
> You replied with:
>
>> Shall be part of v7.
> and yet it ain't part of any v<num>.
>
> Why?
Thanks for taking a look.
From cover letter:
- removed static function names prefix from internal functions (external
used function, such as devm/interrupts-handlers/probe, left with the
prefix to allow stack trace visibility)
As you can see, part of the functions got their prefix removed, e.g.
prepare_msg, handle_ce, handle_ue.
I did take your advise for leaving prefix for having visibility for
functions being used outside. hence, some were left with the prefix.
Let me know what you think.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-16 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 9:51 [PATCH v9 0/2] Amazon's Annapurna Labs Memory Controller EDAC Talel Shenhar
2020-07-28 9:51 ` [PATCH v9 1/2] dt-bindings: edac: al-mc-edac: " Talel Shenhar
2020-07-28 9:51 ` [PATCH v9 2/2] EDAC: al-mc-edac: Introduce " Talel Shenhar
2020-08-15 18:33 ` Borislav Petkov
2020-08-16 9:17 ` Shenhar, Talel [this message]
2020-08-16 11:22 ` Borislav Petkov
2020-08-16 11:35 ` Shenhar, Talel
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=5d516c64-ecd8-6f36-5f95-6708fe0f3fd5@amazon.com \
--to=talel@amazon.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=eitan@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=hanochu@amazon.com \
--cc=hhhawa@amazon.com \
--cc=james.morse@arm.com \
--cc=jonnyc@amazon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=ronenk@amazon.com \
--cc=will@kernel.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).