Ksummit-Discuss Archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "josh@joshtriplett.org" <josh@joshtriplett.org>,
	"dwmw2@infradead.org" <dwmw2@infradead.org>
Cc: "leonro@mellanox.com" <leonro@mellanox.com>,
	"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: Sun, 29 Oct 2017 02:05:47 +0000	[thread overview]
Message-ID: <1509242746.11855.0.camel@wdc.com> (raw)
In-Reply-To: <20171025161655.psufkrr6u62ivmba@jtriplet-mobl2.jf.intel.com>

On Wed, 2017-10-25 at 09:16 -0700, Josh Triplett wrote:
> See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59852 for a proposal to
> implement Sparse's __attribute__((bitwise)) in GCC. The GCC developers
> are amenable, if someone's willing to write a patch.

Thanks Josh. I will have a look at that bugzilla ticket.

Bart.

      reply	other threads:[~2017-10-29  2:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25  9:47 [Ksummit-discuss] [TECH TOPIC] How to encourage driver authors to annotate integer endianness properly 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
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 [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=1509242746.11855.0.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=dwmw2@infradead.org \
    --cc=josh@joshtriplett.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).