From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: u-boot@lists.denx.de
Cc: Tom Rini <trini@konsulko.com>,
linux-snps-arc@lists.infradead.org,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
Rick Chen <rick@andestech.com>,
uboot-snps-arc@synopsys.com
Subject: [RFC 0/2] Import and use non-atomic bit-ops
Date: Mon, 20 Jan 2020 15:43:27 +0300 [thread overview]
Message-ID: <20200120124329.3001-1-abrodkin@synopsys.com> (raw)
The following bitops are implemented pretty similarly for many
arches and now when we faced a need in them on ARC I guess there's
no point in copy-pasting them yet another time but instead it might
be better re-use generic version from the Linux kernel.
Since we had non of those bitops for ARC inclusion of imported header
works perfectly fine. As for other arches I do see they use a bit different
implementation but those might be just older versions etc.
Sobefore breaking stuff for other arches I'd like to get some feedback
from maintainers. Or we may just import proposed header and switch to
its usage arch-by-arch whenever people feel kile cleaning-up their bitops.
Alexey Brodkin (2):
include: Import non-atomic.h from Linux
ARC: Add support of bitops via generic implementation
arch/arc/include/asm/bitops.h | 1 +
include/asm-generic/bitops/non-atomic.h | 109 ++++++++++++++++++++++++++++++++
2 files changed, 110 insertions(+)
create mode 100644 include/asm-generic/bitops/non-atomic.h
--
2.16.2
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next reply other threads:[~2020-01-20 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 12:43 Alexey Brodkin [this message]
2020-01-20 12:43 ` [RFC 1/2] include: Import non-atomic.h from Linux Alexey Brodkin
2020-01-20 12:43 ` [RFC 2/2] ARC: Add support of bitops via generic implementation Alexey Brodkin
2020-01-20 20:38 ` [RFC 0/2] Import and use non-atomic bit-ops 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=20200120124329.3001-1-abrodkin@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=linux-snps-arc@lists.infradead.org \
--cc=rick@andestech.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-snps-arc@synopsys.com \
/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).