From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Doug Ledford' <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
'Woodruff Robert J'
<robert.j.woodruff-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: [PATCH] libibverbs: add ARM64 memory barrier macros
Date: Fri, 20 May 2016 15:20:23 -0500 [thread overview]
Message-ID: <015501d1b2d5$0a020de0$1e0629a0$@opengridcomputing.com> (raw)
In-Reply-To: <2dc25c9c-748c-098c-f7a1-5d6e59504308-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> >> I could utilize the code from FreeBSD. Does that allow me to submit this
to
> >> libibverbs under the dual GPL/BSD license?
> >>
> >
> > I think I can just re-implement these services myself based published works
> > describing the memory barrier assembly for ARM (like the document Jason
> > referenced earlier). That will avoid any tainting.
> >
> > Doug: Will that work?
>
> Either way works actually. IANAL, but I've been told this multiple
> times and will relay my possibly flawed memory of the legal issue. The
> original patch, even though lifted from the linux kernel, is likely to
> fall under the scope of "operationally defined" code. In other words,
> the specific patch you wrote and the thing it implemented is so rigidly
> defined by what it does, that there really is little to no room for any
> different expression of the code. When there is no room for different
> expressions, the code is not copyrightable.
>
That makes too much sense... ;)
--
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
prev parent reply other threads:[~2016-05-20 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 21:16 [PATCH] libibverbs: add ARM64 memory barrier macros Steve Wise
[not found] ` <20160520163207.B99DCE0B9D-/5N3P9jjx0xzbRFIqnYvSA@public.gmane.org>
2016-05-20 16:39 ` Woodruff, Robert J
[not found] ` <9C6B67F36DCAFC479B1CF6A967258A8C7DDBB201-8oqHQFITsIFqS6EAlXoojrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-05-20 18:37 ` Steve Wise
2016-05-20 18:46 ` Steve Wise
2016-05-20 20:17 ` Doug Ledford
[not found] ` <2dc25c9c-748c-098c-f7a1-5d6e59504308-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-05-20 20:20 ` Steve Wise [this message]
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='015501d1b2d5$0a020de0$1e0629a0$@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=robert.j.woodruff-ral2JQCrhuEAvxtiuMwx3w@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