From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'root' <root-6HSsQxwzXLRrcEM49+0neVaTQe2KTcn/@public.gmane.org>,
dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: [PATCH v3 0/2] libibverbs memory barrier fixes
Date: Tue, 7 Jun 2016 11:04:58 -0500 [thread overview]
Message-ID: <01ac01d1c0d6$56b7b770$04272650$@opengridcomputing.com> (raw)
In-Reply-To: <cover.1465310573.git.root-6HSsQxwzXLRrcEM49+0neVaTQe2KTcn/@public.gmane.org>
hmm, root-6HSsQxwzXLRrcEM49+0nea2raWmgRF17@public.gmane.org oops. :)
> -----Original Message-----
> From: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org [mailto:linux-rdma-
> owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org] On Behalf Of root
> Sent: Tuesday, June 07, 2016 9:43 AM
> To: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
> Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> Subject: [PATCH v3 0/2] libibverbs memory barrier fixes
>
> This series implements ARM64 memory barrier support, and fails compiles
> if there is no platform implementation of the memory barriers.
>
> Changes since V3:
>
> white noise fix
>
> parens around asm macros (checkpatch recommendation)
>
> remove RFC tag
>
> Changes since V2:
>
> Implement the mb* macros from scratch
>
> Retested changes on ARM64
>
> Steve Wise (2):
> libibverbs: add ARM64 memory barrier macros
> Fail compiles if no platform specific memory barriers exist
>
> include/infiniband/arch.h | 15 +++++++++------
> 1 files changed, 9 insertions(+), 6 deletions(-)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-06-07 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 14:42 [PATCH v3 0/2] libibverbs memory barrier fixes root
[not found] ` <cover.1465310573.git.root-6HSsQxwzXLRrcEM49+0neVaTQe2KTcn/@public.gmane.org>
2016-06-07 14:42 ` [PATCH 1/2] libibverbs: add ARM64 memory barrier macros Steve Wise
2016-06-07 14:42 ` [PATCH 2/2] Fail compiles if no platform specific memory barriers exist Steve Wise
2016-06-07 16:04 ` Steve Wise [this message]
2016-06-23 14:53 ` [PATCH REPOST v3 0/2] libibverbs memory barrier fixes Doug Ledford
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='01ac01d1c0d6$56b7b770$04272650$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=root-6HSsQxwzXLRrcEM49+0neVaTQe2KTcn/@public.gmane.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