From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] openrisc/bitops: add hweightX defines
Date: Thu, 23 Feb 2012 00:24:49 +0100 [thread overview]
Message-ID: <201202230024.49848.marek.vasut@gmail.com> (raw)
In-Reply-To: <201202221741.19601.vapier@gentoo.org>
> On Wednesday 22 February 2012 17:15:50 Marek Vasut wrote:
> > looks like get_tbclk() and get_ticks() looks all the same just about
> > everywhere. What about introducing a weak alias for these functions so in
> > case weird platform pops up, these can be overridden.
>
> the unified timer core that Graeme/Simon were doing takes care of that
> implicitly
Unified timer core?
M
next prev parent reply other threads:[~2012-02-22 23:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 17:10 [U-Boot] [PATCH 1/2] openrisc/bitops: add hweightX defines Stefan Kristiansson
2012-02-22 17:10 ` [U-Boot] [PATCH] openrisc: implement get_ticks and get_tbclk Stefan Kristiansson
2012-10-02 22:06 ` [U-Boot] " Tom Rini
2012-02-22 17:15 ` [U-Boot] [PATCH 1/2] openrisc/bitops: add hweightX defines Stefan Kristiansson
2012-02-22 22:15 ` Marek Vasut
2012-02-22 22:41 ` Mike Frysinger
2012-02-22 23:24 ` Marek Vasut [this message]
2012-02-22 23:29 ` Graeme Russ
2012-10-02 22:06 ` [U-Boot] [U-Boot,1/2] " Tom Rini
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=201202230024.49848.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.de \
/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