From: Christopher Li <sparse@chrisli.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-sparse@vger.kernel.org, penberg@kernel.org
Subject: Re: [PATCH v2] sparse: add __builtin_va_arg_pack() and __builtin_va_arg_pack_len()
Date: Wed, 24 Jul 2013 09:41:02 -0700 [thread overview]
Message-ID: <CANeU7Qn5pj76zecWoLuSU+c85Va-wU9e4hkLxB-GsvRM-1AV1g@mail.gmail.com> (raw)
In-Reply-To: <1374230020-26826-1-git-send-email-jlayton@redhat.com>
On Fri, Jul 19, 2013 at 3:33 AM, Jeff Layton <jlayton@redhat.com> wrote:
> this patch stops sparse from complaining about them not being defined:
>
> /usr/include/bits/stdio2.h:98:25: error: undefined identifier '__builtin_va_arg_pack'
> /usr/include/bits/stdio2.h:98:25: error: not a function <noident>
>
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
Looks good, will apply.
Chris
prev parent reply other threads:[~2013-07-24 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 12:47 error: undefined identifier '__builtin_va_arg_pack' Jeff Layton
2013-07-18 15:36 ` [PATCH] sparse: add __builtin_va_arg_pack() and __builtin_va_arg_pack_len() Jeff Layton
2013-07-19 2:49 ` Christopher Li
2013-07-19 10:33 ` [PATCH v2] " Jeff Layton
2013-07-24 16:41 ` Christopher Li [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=CANeU7Qn5pj76zecWoLuSU+c85Va-wU9e4hkLxB-GsvRM-1AV1g@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=jlayton@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=penberg@kernel.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;
as well as URLs for NNTP newsgroup(s).