From: Christopher Li <sparse@chrisli.org>
To: Damien Lespiau <damien.lespiau@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Ignore the may_alias GCC attribute
Date: Tue, 1 Jun 2010 15:31:44 -0700 [thread overview]
Message-ID: <AANLkTim4BaJ2JGBU1vUi-GguEZAdZY70Oo070J0hfHoq@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikvGsi4Ju25yduhlszVP3BOiCEEHrlO6hNoGKFV@mail.gmail.com>
On Tue, Jun 1, 2010 at 9:35 AM, Damien Lespiau <damien.lespiau@gmail.com> wrote:
> Unfortunately, linux-sparse seems to reject my git send-emails with
> GMail's SMTP server, so I'm attaching the git format-patch instead.
>
> may_alias is used in the wild (glib) and makes sparse spew a lot of
> unhelpful warning messages. Ignore it (for now?).
>
The patch looks good. Will apply.
Chris
prev parent reply other threads:[~2010-06-01 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 16:35 [PATCH] Ignore the may_alias GCC attribute Damien Lespiau
2010-06-01 22:31 ` 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=AANLkTim4BaJ2JGBU1vUi-GguEZAdZY70Oo070J0hfHoq@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=damien.lespiau@gmail.com \
--cc=linux-sparse@vger.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).