From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH] provide ffs and __ashrdi3 for all architectures
Date: Mon, 25 Jun 2012 14:44:36 +0200 [thread overview]
Message-ID: <1340628281-8774-1-git-send-email-s.hauer@pengutronix.de> (raw)
For upcoming 64bit file support we need ffs and __ashrdi3 functions
for all architectures. These patches provide them.
Sascha
----------------------------------------------------------------
Sascha Hauer (5):
blackfin: add __ashrdi3
openrisc: link to libgcc
mips: Add missing ffs include
nios2: Add missing ffs include
x86: Add missing ffs include
arch/blackfin/lib/Makefile | 1 +
arch/blackfin/lib/ashrdi3.c | 36 ++++++++++++++++++++++++++++++++++++
arch/mips/include/asm/bitops.h | 1 +
arch/nios2/include/asm/bitops.h | 3 +++
arch/openrisc/Makefile | 4 ++++
arch/x86/include/asm/bitops.h | 5 ++++-
6 files changed, 49 insertions(+), 1 deletion(-)
create mode 100644 arch/blackfin/lib/ashrdi3.c
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2012-06-25 12:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 12:44 Sascha Hauer [this message]
2012-06-25 12:44 ` [PATCH 1/5] blackfin: add __ashrdi3 Sascha Hauer
2012-06-25 12:44 ` [PATCH 2/5] openrisc: link to libgcc Sascha Hauer
2012-06-25 13:00 ` Sascha Hauer
2012-06-25 12:44 ` [PATCH 3/5] mips: Add missing ffs include Sascha Hauer
2012-06-25 12:44 ` [PATCH 4/5] nios2: " Sascha Hauer
2012-06-25 12:44 ` [PATCH 5/5] x86: " Sascha Hauer
2012-09-05 20:37 ` [PATCH] [OpenRISC] Add __ashrdi3 and remove link to libgcc Franck Jullien
2012-09-06 6:55 ` Sascha Hauer
2012-09-06 7:28 ` Franck Jullien
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=1340628281-8774-1-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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