All of lore.kernel.org
 help / color / mirror / Atom feed
From: root <root-6HSsQxwzXLRrcEM49+0neVaTQe2KTcn/@public.gmane.org>
To: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v3 0/2] libibverbs memory barrier fixes
Date: Tue, 7 Jun 2016 07:42:53 -0700	[thread overview]
Message-ID: <cover.1465310573.git.root@r9.asicdesigners.com> (raw)

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

             reply	other threads:[~2016-06-07 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07 14:42 root [this message]
     [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   ` [PATCH v3 0/2] libibverbs memory barrier fixes Steve Wise
2016-06-23 14:53   ` [PATCH REPOST " 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=cover.1465310573.git.root@r9.asicdesigners.com \
    --to=root-6hssqxwzxlrrcem49+0nevatqe2ktcn/@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 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.