public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH rdma-core 2/5] ccan: Add CCAN min and max functionality
Date: Wed, 28 Sep 2016 10:18:25 -0600	[thread overview]
Message-ID: <20160928161825.GA22668@obsidianresearch.com> (raw)
In-Reply-To: <1475076789-14359-3-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

On Wed, Sep 28, 2016 at 06:33:06PM +0300, Yishai Hadas wrote:

> +publish_internal_headers(ccan
> +  minmax.h
> +  build_assert.h
> +  config.h
> +  )

Please keep these lists in cmakefiles sorted everywhere, in every
patch.

> diff --git a/ccan/config.h b/ccan/config.h
> new file mode 100644
> index 0000000..b89ac94
> +++ b/ccan/config.h
> @@ -0,0 +1,2 @@
> +#define HAVE_STATEMENT_EXPR 1
> +#define HAVE_TYPEOF 1

This is going to get confusing, ditch this and just put those lines in
buildlib/config.h.in

I think you'll need to add a header sentinal to config.h.in to guard
against multiple inclusion, I forgot apparently.

> +#if HAVE_BUILTIN_TYPES_COMPATIBLE_P

Add to config.h.in

> +++ b/ccan/build_assert.h
> @@ -0,0 +1,40 @@
> +/* CC0 (Public domain) - see LICENSE file for details */

Each patch also needs to add the appropriate COPYING/LICENSE files to ccan/

Jason
--
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

  parent reply	other threads:[~2016-09-28 16:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28 15:33 [PATCH rdma-core 0/5] Licensing and cleanup issues Yishai Hadas
     [not found] ` <1475076789-14359-1-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-09-28 15:33   ` [PATCH rdma-core 1/5] Remove container_of and offset local declarations Yishai Hadas
2016-09-28 15:33   ` [PATCH rdma-core 2/5] ccan: Add CCAN min and max functionality Yishai Hadas
     [not found]     ` <1475076789-14359-3-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-09-28 16:18       ` Jason Gunthorpe [this message]
2016-09-28 15:33   ` [PATCH rdma-core 3/5] ccan: Add list functionality Yishai Hadas
     [not found]     ` <1475076789-14359-4-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-09-28 16:53       ` Jason Gunthorpe
2016-09-28 15:33   ` [PATCH rdma-core 4/5] libmlx5: Move to use CCAN " Yishai Hadas
2016-09-28 15:33   ` [PATCH rdma-core 5/5] libocrdma: " Yishai Hadas
     [not found]     ` <1475076789-14359-6-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-09-29  3:02       ` Devesh Sharma
2016-09-28 16:03   ` [PATCH rdma-core 0/5] Licensing and cleanup issues Doug Ledford
2016-09-28 17:26   ` Jason Gunthorpe

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=20160928161825.GA22668@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@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