From: Borislav Petkov <bp@alien8.de>
To: Stefan Schaeckeler <schaecsn@gmx.net>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, joel@jms.id.au,
andrew@aj.id.au, mchehab@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-edac@vger.kernel.org,
sschaeck@cisco.com
Subject: Re: [PATCH 1/2] EDAC: Add Aspeed AST2500 EDAC driver
Date: Wed, 16 Jan 2019 22:30:59 +0100 [thread overview]
Message-ID: <20190116213059.GM15409@zn.tnic> (raw)
In-Reply-To: <20190115175749.01E3C6E85603@corona.crabdance.com>
On Tue, Jan 15, 2019 at 09:57:48AM -0800, Stefan Schaeckeler wrote:
> That's interesting. I did a grep over all 16944 GPL licensed files with an SPDX
> identifier.
>
> 785 of them have a license text while 16159 don't.
Goes to show that we're still in the process of converting stuff to SPDX.
> When stripping off aspeed_edac_, some static function names will become quite
> "bare-bone":
>
> aspeed_edac_init(), aspeed_edac_exit(), aspeed_edac_probe(),
> aspeed_edac_remove(), aspeed_edac_of_match(), aspeed_edac_isr(),
> aspeed_edac_config_irq().
So namespaced function names we normally use for globally visible
symbols and those are not but only driver-specific. So, for example,
aspeed_edac_config_irq()
is a mouthful, at least to me, and not needed. config_irq(), OTOH, is
clear at a very quick glance.
The others, aspeed_edac_init(), etc, you could call aspeed_init(),
aspeed_exit() or so.
But since you're going to be stare at that code, this was just a
suggestion. Your call. :)
> Does your suggestion also apply to static variables? E.g. aspeed_edac_regmap,
> aspeed_edac_regmap_config, aspeed_edac_driver? Also, here some variable names
> would become quite "bare-bone".
Same as above.
HTH.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-01-16 21:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 6:01 [PATCH 0/2] Add support for the Aspeed AST2500 SoC EDAC driver Stefan Schaeckeler
2018-12-17 6:01 ` [PATCH 1/2] EDAC: Add Aspeed AST2500 " Stefan Schaeckeler
2018-12-31 13:20 ` Stefan Schaeckeler
2018-12-31 13:53 ` Boris Petkov
2019-01-10 9:50 ` Borislav Petkov
2019-01-15 17:57 ` Stefan Schaeckeler
2019-01-16 21:30 ` Borislav Petkov [this message]
2018-12-17 6:01 ` [PATCH 2/2] dt-bindings: edac: Aspeed AST2500 Stefan Schaeckeler
2018-12-27 22:09 ` Rob Herring
2018-12-29 18:30 ` schaecsn
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=20190116213059.GM15409@zn.tnic \
--to=bp@alien8.de \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.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=schaecsn@gmx.net \
--cc=sschaeck@cisco.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).