From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "leonro@mellanox.com" <leonro@mellanox.com>,
"greg@kroah.com" <greg@kroah.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] How to encourage driver authors to annotate integer endianness properly
Date: Wed, 25 Oct 2017 12:11:43 +0000 [thread overview]
Message-ID: <1508933501.4165.15.camel@wdc.com> (raw)
In-Reply-To: <20171025103852.GA26864@kroah.com>
On Wed, 2017-10-25 at 12:38 +0200, greg@kroah.com wrote:
> endian support in sparse has been there for over a decade now, right?
> This isn't a new issue, and if a driver author/team does not want to
> do the work for a specific endian, then disable the drivers from that
> build...
Hello Greg,
Sorry if I wasn't clear enough. My concern is not about drivers that do
not work for a specific endianness but about drivers that need endianness
conversions because the endianness of the firmware registers differs from
that of the CPU. Such drivers benefit from endianness annotations even
if only one specific CPU endianness type is supported by these drivers.
Bart.
next prev parent reply other threads:[~2017-10-25 12:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 9:47 Bart Van Assche
2017-10-25 9:54 ` Greg KH
2017-10-25 10:06 ` Bart Van Assche
2017-10-25 10:13 ` greg
2017-10-25 10:16 ` Mark Brown
2017-10-25 12:56 ` Theodore Ts'o
2017-10-25 10:24 ` Leon Romanovsky
2017-10-25 10:38 ` greg
2017-10-25 12:11 ` Bart Van Assche [this message]
2017-10-25 10:18 ` Leon Romanovsky
2017-10-25 12:40 ` Alexey Dobriyan
2017-10-25 13:11 ` David Woodhouse
2017-10-25 16:16 ` Josh Triplett
2017-10-29 2:05 ` Bart Van Assche
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=1508933501.4165.15.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=greg@kroah.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=leonro@mellanox.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