From: Ashutosh Dixit <ashutosh.dixit@intel.com>
To: Dan Streetman <ddstreet@ieee.org>
Cc: Jonathan Corbet <corbet@lwn.net>, Jiri Kosina <jkosina@suse.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peter Foley <pefoley2@pefoley.com>,
Seth Jennings <sjennings@variantweb.net>,
Randy Dunlap <rdunlap@infradead.org>, "Yokoyama\,
Caz" <caz.yokoyama@intel.com>, "Chandramouli\,
Dasaratharaman" <dasaratharaman.chandramouli@intel.com>, "Dutt\,
Sudeep" <sudeep.dutt@intel.com>,
"linux-doc\@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation/mic/mpssd: fix compile error on BE platforms
Date: Thu, 04 Dec 2014 13:33:10 -0800 [thread overview]
Message-ID: <m3tx1bt815.fsf@adixit-yct.ra.intel.com> (raw)
In-Reply-To: <1417708875-32189-1-git-send-email-ddstreet@ieee.org> (Dan Streetman's message of "Thu, 4 Dec 2014 09:01:15 -0700")
On Thu, Dec 04 2014 at 08:01:15 AM, Dan Streetman <ddstreet@ieee.org> wrote:
> Change any use of htole* macro in static context to instead manually check
> for endianness and use __bswap_constant_* macro instead.
>
> The current glibc definitions of the htole* macros don't allow their use
> in a static context; on big endian systems the build fails with:
Instead of building Documentation/mic/mpssd for all architectures, I
have submitted a patch which would build it only for x86_64 since that
is the only place where it will ever be used. This would resolve this
and future builds breaks and also make this patch unnecessary. The
maintainers can decide to accept either or these patches, or even both.
prev parent reply other threads:[~2014-12-04 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 0:07 v3.18-rc5 build failure on ppc64 in Documentation/mic/mpssd/mpssd.o Seth Jennings
2014-11-20 10:49 ` Jiri Kosina
2014-12-04 16:01 ` [PATCH] Documentation/mic/mpssd: fix compile error on BE platforms Dan Streetman
2014-12-04 21:33 ` Ashutosh Dixit [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=m3tx1bt815.fsf@adixit-yct.ra.intel.com \
--to=ashutosh.dixit@intel.com \
--cc=caz.yokoyama@intel.com \
--cc=corbet@lwn.net \
--cc=dasaratharaman.chandramouli@intel.com \
--cc=ddstreet@ieee.org \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pefoley2@pefoley.com \
--cc=rdunlap@infradead.org \
--cc=sjennings@variantweb.net \
--cc=sudeep.dutt@intel.com \
/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
Powered by JetHome