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: Wed, 22 Feb 2012 23:15:50 +0100 [thread overview]
Message-ID: <201202222315.51042.marek.vasut@gmail.com> (raw)
In-Reply-To: <20120222171502.GA14563@chokladfabriken.org>
> On Wed, Feb 22, 2012 at 07:10:09PM +0200, Stefan Kristiansson wrote:
> > Signed-off-by: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
> > ---
> >
> > arch/openrisc/include/asm/bitops.h | 4 ++++
> > 1 files changed, 4 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch/openrisc/include/asm/bitops.h
> > b/arch/openrisc/include/asm/bitops.h index c001a5d..c76a409 100644
> > --- a/arch/openrisc/include/asm/bitops.h
> > +++ b/arch/openrisc/include/asm/bitops.h
> > @@ -25,4 +25,8 @@
> >
> > #define PLATFORM_FFS
> > #include <asm/bitops/ffs.h>
> >
> > +#define hweight32(x) generic_hweight32(x)
> > +#define hweight16(x) generic_hweight16(x)
> > +#define hweight8(x) generic_hweight8(x)
> > +
> >
> > #endif /* __ASM_GENERIC_BITOPS_H */
>
> Sorry, screwed up when I format-patched this,
> there is no part 2 to it.
>
Hey,
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.
M
next prev parent reply other threads:[~2012-02-22 22:15 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 [this message]
2012-02-22 22:41 ` Mike Frysinger
2012-02-22 23:24 ` Marek Vasut
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=201202222315.51042.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.