From: Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>
To: "Lothar Waßmann" <LW-bxm8fMRDkQLDiMYJYoSAnRvVK+yQ3ZXh@public.gmane.org>
Cc: Loc Ho <lho-qTEPVZfXA3Y@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Jon Masters <jcm-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Mauro Carvalho Chehab
<mchehab-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>,
"patches-qTEPVZfXA3Y@public.gmane.org"
<patches-qTEPVZfXA3Y@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Doug Thompson
<dougthompson-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
linux-edac-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v3 1/4] edac: Add an function to retrieve the EDAC debugfs node
Date: Thu, 13 Aug 2015 10:52:01 +0200 [thread overview]
Message-ID: <20150813085201.GC20004@nazgul.tnic> (raw)
In-Reply-To: <20150813104150.2c084a8c-VjFSrY7JcPWvSplVBqRQBQ@public.gmane.org>
On Thu, Aug 13, 2015 at 10:41:50AM +0200, Lothar Waßmann wrote:
> What's the point in having an accessor function that returns a driver
> internal variable when this variable is exported anyway?
Not driver-internal but EDAC-core internal.
> This will only further inconsistencies because half of the users will
> use the variable directly and the other half will use the accessor
> function.
The idea is that it is not visible outside of EDAC. The EDAC drivers
themselves should see it. And yes, I admit that the accessors are maybe
redundant then since EDAC drivers can use edac_debugfs ptr directly.
Hmm, and that's ok too because my other concern about future refactoring
is taken care of too because as long as all users of edac_debugfs are
confined to drivers/edac/, changing stuff there is easy.
Ok, I'm convinced, Loc, feel free to drop the accessors in your next
version.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-08-13 8:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 20:47 [PATCH v3 0/4] edac: Add L3/SoC support to the APM X-Gene SoC EDAC driver Loc Ho
[not found] ` <1439326077-25507-1-git-send-email-lho-qTEPVZfXA3Y@public.gmane.org>
2015-08-11 20:47 ` [PATCH v3 1/4] edac: Add an function to retrieve the EDAC debugfs node Loc Ho
[not found] ` <1439326077-25507-2-git-send-email-lho-qTEPVZfXA3Y@public.gmane.org>
2015-08-11 20:47 ` [PATCH v3 2/4] Documentation: Update the APM X-Gene SoC EDAC DTS binding for L3/SoC subnodes Loc Ho
[not found] ` <1439326077-25507-3-git-send-email-lho-qTEPVZfXA3Y@public.gmane.org>
2015-08-11 20:47 ` [PATCH v3 3/4] edac: Add L3/SoC EDAC support to the APM X-Gene SoC EDAC driver Loc Ho
[not found] ` <1439326077-25507-4-git-send-email-lho-qTEPVZfXA3Y@public.gmane.org>
2015-08-11 20:47 ` [PATCH v3 4/4] arm64: Add L3/SoC DT subnodes to the APM X-Gene SoC EDAC node Loc Ho
2015-08-12 10:51 ` [PATCH v3 3/4] edac: Add L3/SoC EDAC support to the APM X-Gene SoC EDAC driver Borislav Petkov
[not found] ` <20150812105121.GE14011-K5JNixvcfoxupOikMc4+xw@public.gmane.org>
2015-08-12 17:50 ` Loc Ho
[not found] ` <CAPw-ZTkRytHUsUsDmTkfzzTYbcZnmTVRMkzNzg_9ZpdQH76rZw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-13 3:36 ` Borislav Petkov
[not found] ` <20150813033640.GB14432-K5JNixvcfoxupOikMc4+xw@public.gmane.org>
2015-08-13 4:13 ` Loc Ho
2015-08-12 10:12 ` [PATCH v3 1/4] edac: Add an function to retrieve the EDAC debugfs node Borislav Petkov
[not found] ` <20150812101219.GC14011-K5JNixvcfoxupOikMc4+xw@public.gmane.org>
2015-08-12 10:49 ` Borislav Petkov
[not found] ` <20150812104954.GD14011-K5JNixvcfoxupOikMc4+xw@public.gmane.org>
2015-08-12 17:23 ` Loc Ho
2015-08-13 3:38 ` Borislav Petkov
2015-08-13 4:30 ` Loc Ho
[not found] ` <CAPw-ZTkfAxqG6HQHU3WomrqRwXa+jyTWCg=ns1HKC323ds1yug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-13 8:15 ` Borislav Petkov
[not found] ` <20150813081537.GB20004-K5JNixvcfoxupOikMc4+xw@public.gmane.org>
2015-08-13 8:41 ` Lothar Waßmann
[not found] ` <20150813104150.2c084a8c-VjFSrY7JcPWvSplVBqRQBQ@public.gmane.org>
2015-08-13 8:52 ` Borislav Petkov [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=20150813085201.GC20004@nazgul.tnic \
--to=bp-gina5biwoiwzqb+pc5nmwq@public.gmane.org \
--cc=LW-bxm8fMRDkQLDiMYJYoSAnRvVK+yQ3ZXh@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dougthompson-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
--cc=jcm-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=lho-qTEPVZfXA3Y@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-edac-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=mchehab-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org \
--cc=patches-qTEPVZfXA3Y@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).