From: Josh Triplett <josh@freedesktop.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH 2/3] fix show_typename()
Date: Thu, 03 Apr 2008 13:46:09 -0700 [thread overview]
Message-ID: <47F54211.5050600@freedesktop.org> (raw)
In-Reply-To: <E1JSgxJ-0003m5-1z@ZenIV.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
Al Viro wrote:
> * postfix stuff had been applied in wrong order (e.g. int a[2][3] generated
> int [addressable][toplevel] a[3][2])
> * after fixing that, we've no need for recursion anymore, a bunch of arguments
> go away and turn into local variables and we get an easy way to get rid of
> bogus space in the show_typename() result.
>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Applied, along with corresponding changes to the test suite, and pushed.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2008-04-03 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 23:05 [PATCH 2/3] fix show_typename() Al Viro
2008-04-03 20:46 ` Josh Triplett [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=47F54211.5050600@freedesktop.org \
--to=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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 NNTP newsgroup(s).