From: Christopher Li <sparse@chrisli.org>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>, linux-s390@vger.kernel.org
Subject: Re: [PATCH] s390x: add the proper defines for data types
Date: Thu, 22 Jan 2015 09:52:56 -0800 [thread overview]
Message-ID: <CANeU7Qn9jD-ZX2CjSkVTyTu92b9qwM4XZqTOSUB5NDVpAdVMSQ@mail.gmail.com> (raw)
In-Reply-To: <1421920310-1499-1-git-send-email-borntraeger@de.ibm.com>
On Thu, Jan 22, 2015 at 1:51 AM, Christian Borntraeger
<borntraeger@de.ibm.com> wrote:
> This patch fixes several issues when compiling code under s390x
> (64bit) with cgcc, e.g.
> /usr/include/gnu/stubs.h:8:12: error: unable to open 'gnu/stubs-32.h'
> by providing the proper defines.
The change looks good. Will apply.
Chris
prev parent reply other threads:[~2015-01-22 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 9:51 [PATCH] s390x: add the proper defines for data types Christian Borntraeger
2015-01-22 13:50 ` [PATCH] s390x: add the proper defines for data types (sparse) Christian Borntraeger
2015-01-22 17:52 ` 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=CANeU7Qn9jD-ZX2CjSkVTyTu92b9qwM4XZqTOSUB5NDVpAdVMSQ@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=borntraeger@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--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).