From: David Gibson <david@gibson.dropbear.id.au>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: ccan@lists.ozlabs.org
Subject: Re: [PATCH 2/2] ccanlint: Move ccanlint test options from _info comments to code
Date: Thu, 29 Dec 2016 19:01:23 +1100 [thread overview]
Message-ID: <20161229080123.GA18749@umbus.fritz.box> (raw)
In-Reply-To: <871swuf3is.fsf@rustcorp.com.au>
[-- Attachment #1.1: Type: text/plain, Size: 970 bytes --]
On Tue, Dec 27, 2016 at 02:05:07PM +1030, Paul 'Rusty' Russell wrote:
> David Gibson <david@gibson.dropbear.id.au> writes:
> > Currently, _info files can specify options, or note expected failures, for
> > ccanlint checks in the _info file with specially structured comments. That
> > differs from most other things ccanlint gets from _info, where it instead
> > executes the info file with certain parameters.
> >
> > This changes ccanlint and existing _info files to use the normal method for
> > the ccanlint test options as well. This also has the advantage that an
> > info file can alter its test options based on things from config.h - in
> > some cases whether a test can work or not might depend on various things.
>
> Agreed, please apply!
Done.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
ccan mailing list
ccan@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/ccan
prev parent reply other threads:[~2016-12-29 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 4:49 [PATCH 1/2] Makefile: Make module checks depend on info file David Gibson
2016-12-25 4:49 ` [PATCH 2/2] ccanlint: Move ccanlint test options from _info comments to code David Gibson
2016-12-27 3:35 ` Rusty Russell
2016-12-29 8:01 ` David Gibson [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=20161229080123.GA18749@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=ccan@lists.ozlabs.org \
--cc=rusty@rustcorp.com.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