From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] testsuite: fix parsing of tags used in the testcases
Date: Fri, 11 Dec 2020 21:14:22 +0100 [thread overview]
Message-ID: <20201211201422.meemxz2bx5gqbxuu@ltop.local> (raw)
In-Reply-To: <4176615c-73b8-ff5e-d705-f6a71ea49cab@ramsayjones.plus.com>
On Fri, Dec 11, 2020 at 04:39:15PM +0000, Ramsay Jones wrote:
>
> I needed to apply this to get the testsuite to pass on tonights
> 'fetch'. However, my immediate thought was 'what if you had more
> than one space before/after the '*'?
>
> It just so happens that I had a couple of 'warning: <file>: test unhandled'
> after applying the patch (for asm-empty-clobber.c and asm-goto-labels.c)
> where they had two spaces after the '*', so ... :-D
Yes, I messed up twice here :(
Thanks for noticing.
-- Luc
prev parent reply other threads:[~2020-12-11 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 13:06 [PATCH] testsuite: fix parsing of tags used in the testcases Luc Van Oostenryck
2020-12-11 16:39 ` Ramsay Jones
2020-12-11 20:14 ` Luc Van Oostenryck [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=20201211201422.meemxz2bx5gqbxuu@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).