From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: RE: [PATCH 0/4] libcxgb4: header file/copyright clean up
Date: Fri, 30 Sep 2016 15:31:07 -0500 [thread overview]
Message-ID: <0a2a01d21b59$92b6ab90$b82402b0$@opengridcomputing.com> (raw)
In-Reply-To: <09b401d21b39$0fff6f90$2ffe4eb0$@opengridcomputing.com>
> > These patches clean up the header files in libcxgb4 by synching them
> > with the equivalent upstream versions. The net result of this is proper
> > dual license copyrights. I also got rid of the libcxgb4/src/queue.h and
> > replaced it with the ccan list header.
>
> I also create a pull request on github. I _think_ it is correct :)
>
> https://github.com/linux-rdma/rdma-core/pull/11
And patch 2 didn't make it, probably due to its size. You can review it via
the pull request if you wish.
Steve
--
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-09-30 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 16:35 [PATCH 0/4] libcxgb4: header file/copyright clean up Steve Wise
[not found] ` <cover.1475253317.git.swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2016-09-30 16:10 ` [PATCH 1/4] libcxgb4: align header files with upstream kernel Steve Wise
2016-09-30 16:29 ` [PATCH 3/4] libcxgb4: replace t4fw_interface.h with upstream kernel headers Steve Wise
2016-09-30 16:29 ` [PATCH 4/4] libcxgb4: use ccan lists Steve Wise
2016-09-30 16:38 ` [PATCH 0/4] libcxgb4: header file/copyright clean up Steve Wise
2016-09-30 20:31 ` Steve Wise [this message]
2016-10-02 13:12 ` 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='0a2a01d21b59$92b6ab90$b82402b0$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox