From: Tony Camuso <tcamuso@redhat.com>
To: linux-sparse@vger.kernel.org
Subject: Re: sparse error: got __int128
Date: Sun, 18 Jan 2015 07:29:59 -0500 [thread overview]
Message-ID: <54BBA747.1040204@redhat.com> (raw)
In-Reply-To: <54BBA6E4.7020506@redhat.com>
On 01/18/2015 07:28 AM, Tony Camuso wrote:
>
> Of course, disabling 64-bit kernel in .config removes the problem, but this is
> an unacceptable solution.
^^^
NOT
prev parent reply other threads:[~2015-01-18 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 12:28 sparse error: got __int128 Tony Camuso
2015-01-18 12:29 ` Tony Camuso [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=54BBA747.1040204@redhat.com \
--to=tcamuso@redhat.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).