From: Thomas Gleixner <tglx@linutronix.de>
To: Xiubo Li <Li.Xiubo@freescale.com>
Cc: daniel.lezcano@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clocksource: Add BE/LE APIs support for clocksource counter reading.
Date: Wed, 10 Sep 2014 22:33:52 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1409102212530.4178@nanos> (raw)
In-Reply-To: <1410340819-35110-1-git-send-email-Li.Xiubo@freescale.com>
On Wed, 10 Sep 2014, Xiubo Li wrote:
So you add BE/LE APIs according to the subject line, but you fail
again to tell WHY. If that would be the only issue ....
> Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
> ---
> drivers/clocksource/mmio.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 44 insertions(+)
>
> diff --git a/drivers/clocksource/mmio.c b/drivers/clocksource/mmio.c
> index 1593ade..ddc5214 100644
> --- a/drivers/clocksource/mmio.c
> +++ b/drivers/clocksource/mmio.c
So you think that adding this to mmio.c is the solution to the
problem?
Ever heard about function prototypes, header files and such?
> @@ -20,21 +20,65 @@ static inline struct clocksource_mmio *to_mmio_clksrc(struct clocksource *c)
> return container_of(c, struct clocksource_mmio, clksrc);
> }
>
> +cycle_t clocksource_mmio_readl_up_be(struct clocksource *c)
> +{
> + return (cycle_t)be32_to_cpu(readl_relaxed(to_mmio_clksrc(c)->reg));
> +}
> +
> +cycle_t clocksource_mmio_readl_up_le(struct clocksource *c)
> +{
> + return (cycle_t)le32_to_cpu(readl_relaxed(to_mmio_clksrc(c)->reg));
> +}
> +
> cycle_t clocksource_mmio_readl_up(struct clocksource *c)
> {
> return (cycle_t)readl_relaxed(to_mmio_clksrc(c)->reg);
> }
So now we have three global functions which provide access to the mmio
clocksource. And one of them is always redundant for a given compile
time endianess. You can't be serious about this...
But ... wait, I've seen enough qualitee code from Fleascale in the
past 10 years, so you actually might be serious about it.
JFYI: You are trying to submit code to the public maintained codebase
of the Linux kernel, not to some random sh^H^Hgit repository inside of
Fleascale which accepts any random amount of crap. Can you see the
difference?
I can see it rather clearly.
Thanks,
tglx
next prev parent reply other threads:[~2014-09-10 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 9:20 Xiubo Li
2014-09-10 20:33 ` Thomas Gleixner [this message]
2014-09-11 2:32 ` Li.Xiubo
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=alpine.DEB.2.10.1409102212530.4178@nanos \
--to=tglx@linutronix.de \
--cc=Li.Xiubo@freescale.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®