From: Rusty Russell <rusty@rustcorp.com.au>
To: David Gibson <david@gibson.dropbear.id.au>, ccan@lists.ozlabs.org
Subject: Re: [PATCH 2/2] Build info files
Date: Tue, 24 May 2016 14:16:39 +0930 [thread overview]
Message-ID: <87k2ik5ahc.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1462823981-1972-3-git-send-email-david@gibson.dropbear.id.au>
David Gibson <david@gibson.dropbear.id.au> writes:
> All modules have a _info file (a C file, despite the lack of extension)
> giving metadata for the module. The Makefiles have a rule to build these..
> but it's broken (missing an include directive).
>
> This patch fixes the rule, and builds the info binaries for all modules by
> default. This is a useful check and also useful for manually inspecting
> a module's metadata.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Sorry for the delay. These are great, please apply.
Thanks!
Rusty.
_______________________________________________
ccan mailing list
ccan@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/ccan
next prev parent reply other threads:[~2016-05-24 4:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 19:59 [PATCH 0/2] More build cleanups David Gibson
2016-05-09 19:59 ` [PATCH 1/2] Automatically determine which modules have source David Gibson
2016-05-09 19:59 ` [PATCH 2/2] Build info files David Gibson
2016-05-24 4:46 ` Rusty Russell [this message]
2016-05-24 11:13 ` David Gibson
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=87k2ik5ahc.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=ccan@lists.ozlabs.org \
--cc=david@gibson.dropbear.id.au \
/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