linux-kernel - Re: [PATCHv2 1/4] Clocksource: Flextimer: Use internal clocksource read API.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.10.1409051730270.5472@nanos>
Date:	Fri, 5 Sep 2014 17:40:28 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Xiubo Li <Li.Xiubo@...escale.com>
cc:	daniel.lezcano@...aro.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2 1/4] Clocksource: Flextimer: Use internal clocksource
 read API.

On Fri, 5 Sep 2014, Xiubo Li wrote:

> Since the Flextimer device will be implemented in BE mode on
> LS1 SoC, and in LE mode on Vybrid, LS2 SoCs, so here we need
> the endianness judgment before doing the mmio.

WTF? I explained you in great length HOW you should solve that, but
you just ignore it. Instead of trying to understand what I say you
just resend the same nonsense again.

Keep that attitude up, if you want to make sure, that your patches are
ignored in the future.

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/