From: "Steven J. Hill" <Steven.Hill@imgtec.com>
To: LMOL <linux-mips@linux-mips.org>
Subject: Broken patch for LONG_LONG_MAX.
Date: Thu, 24 Apr 2014 11:01:39 -0500 [thread overview]
Message-ID: <53593563.9030904@imgtec.com> (raw)
Ralf,
In commit e80016dd6b2805339b6b5e2a2ea6d49ab9fa25b6 you deleted checking
for LONG_LONG_MAX which breaks on newer toolchains using the gcc-4.8.x
compilers. Might I suggest usage of LLONG_MAX instead? Thanks.
Steve
reply other threads:[~2014-04-24 16:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53593563.9030904@imgtec.com \
--to=steven.hill@imgtec.com \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.