From: Vineet.Gupta1@synopsys.com (Vineet Gupta)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH v3 0/2] Getting rid of CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
Date: Mon, 12 Sep 2016 10:58:01 -0700 [thread overview]
Message-ID: <1473703083-8625-1-git-send-email-vgupta@synopsys.com> (raw)
In-Reply-To: <201609111259.q67d9T4B%fengguang.wu@intel.com>
Hi Peter / Tony.
Sorry for the rebase snafu with v2.
So kbuild service reported build failure of ia64 with v1 of the patch.
I've added an untested atomic64_dec_if_positive() to ia64, shamelessly
copied from s390 with some adjustments 64-bit long etc. Could you please
double check.
It builds fine with ia64 cross compiler.
Thx,
-Vineet
*** BLURB HERE ***
Vineet Gupta (2):
ia64: implement atomic64_dec_if_positive
atomic64: No need for CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
arch/alpha/Kconfig | 1 -
arch/arm/Kconfig | 1 -
arch/arm64/Kconfig | 1 -
arch/ia64/include/asm/atomic.h | 16 ++++++++++++++++
arch/mips/Kconfig | 1 -
arch/parisc/Kconfig | 1 -
arch/powerpc/Kconfig | 1 -
arch/s390/Kconfig | 1 -
arch/sparc/Kconfig | 1 -
arch/tile/Kconfig | 1 -
arch/x86/Kconfig | 1 -
lib/Kconfig | 3 ---
lib/atomic64_test.c | 4 ----
13 files changed, 16 insertions(+), 17 deletions(-)
--
2.7.4
next prev parent reply other threads:[~2016-09-12 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 16:28 [PATCH] atomic64: No need for CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE Vineet Gupta
2016-09-08 18:19 ` Peter Zijlstra
2016-09-08 18:34 ` Vineet Gupta
2016-09-11 4:31 ` kbuild test robot
2016-09-12 17:58 ` Vineet Gupta [this message]
2016-09-12 17:58 ` [PATCH v3 1/2] ia64: implement atomic64_dec_if_positive Vineet Gupta
2016-09-12 17:58 ` [PATCH v3 2/2] atomic64: No need for CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE Vineet Gupta
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=1473703083-8625-1-git-send-email-vgupta@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=linux-snps-arc@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;
as well as URLs for NNTP newsgroup(s).