From: Christoph Hellwig <hch@lst.de>
To: Maciej Rozycki <macro@wdc.com>
Cc: Christoph Hellwig <hch@lst.de>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"mick@ics.forth.gr" <mick@ics.forth.gr>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH, RFC] byteorder: sanity check toolchain vs kernel endianess
Date: Thu, 30 May 2019 08:41:31 +0200 [thread overview]
Message-ID: <20190530064131.GA29291@lst.de> (raw)
In-Reply-To: <alpine.DEB.2.20.1905300243200.18422@tpp.hgst.com>
On Thu, May 30, 2019 at 01:46:18AM +0000, Maciej Rozycki wrote:
> > +#if defined(__BYTE_ORDER__) && __BYTE_ORDER__ != __ORDER_BIG_ENDIAN__
> > +#error "Unsupported endianess, check your toolchain"
>
> Typo here: s/endianess/endianness/.
The original patch has already been merged, please send a fixup.
prev parent reply other threads:[~2019-05-30 6:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 14:35 [PATCH, RFC] byteorder: sanity check toolchain vs kernel endianess Christoph Hellwig
2019-04-12 14:53 ` Arnd Bergmann
2019-04-12 14:55 ` Christoph Hellwig
2019-04-12 15:22 ` Arnd Bergmann
2019-04-12 16:05 ` Nick Kossifidis
2019-05-10 10:53 ` Dmitry Vyukov
2019-05-11 0:51 ` Arnd Bergmann
2019-05-11 0:51 ` Arnd Bergmann
2019-05-13 7:39 ` Dmitry Vyukov
2019-05-13 7:39 ` Dmitry Vyukov
2019-05-13 11:33 ` Michael Ellerman
2019-05-13 11:33 ` Michael Ellerman
2019-05-13 11:50 ` Dmitry Vyukov
2019-05-13 11:50 ` Dmitry Vyukov
2019-05-13 12:04 ` Christoph Hellwig
2019-05-13 12:04 ` Christoph Hellwig
2019-05-15 6:53 ` Arnd Bergmann
2019-05-15 6:53 ` Arnd Bergmann
2019-05-30 1:46 ` Maciej Rozycki
2019-05-30 6:41 ` Christoph Hellwig [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=20190530064131.GA29291@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@wdc.com \
--cc=mick@ics.forth.gr \
--cc=torvalds@linux-foundation.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.