From: Al Viro <viro@zeniv.linux.org.uk>
To: Gal Pressman <galpress@amazon.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Joe Perches <joe@perches.com>,
Bart Van Assche <bvanassche@acm.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Tariq Toukan <tariqt@mellanox.com>,
xavier.huwei@huawei.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, Doug Ledford <dledford@redhat.com>,
Stephen Warren <swarren@nvidia.com>,
Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org
Subject: Re: rfc: bool structure members (was Re: [PATCH V3] net/mlx4: Get rid of page operation after dma_alloc_coherent)
Date: Sun, 23 Dec 2018 16:53:12 +0000 [thread overview]
Message-ID: <20181223165312.GE2217@ZenIV.linux.org.uk> (raw)
In-Reply-To: <dc6d4923-63bd-e133-310b-7b164b0c92f5@amazon.com>
On Sun, Dec 23, 2018 at 06:42:20PM +0200, Gal Pressman wrote:
> > -17) Don't re-invent the kernel macros
> > +17) Using bool
> > +--------------
> > +
> > +The Linux kernel uses the C11 standard for the bool type. bool values can only
C99, surely?
next prev parent reply other threads:[~2018-12-23 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181219182031.8675-1-swarren@wwwdotorg.org>
[not found] ` <20181220174318.GA21404@ziepe.ca>
[not found] ` <20181220174448.GA21149@lst.de>
[not found] ` <1545328145.185366.500.camel@acm.org>
[not found] ` <072c2d9d187daf0672bf54ab035e47a05fd1cd1d.camel@perches.com>
[not found] ` <20181221033159.GF23877@ziepe.ca>
[not found] ` <b906bec0fd12d25474561263087a26b8b0519fe4.camel@perches.com>
2018-12-21 23:52 ` rfc: bool structure members (was Re: [PATCH V3] net/mlx4: Get rid of page operation after dma_alloc_coherent) Jason Gunthorpe
2018-12-23 16:42 ` Gal Pressman
2018-12-23 16:53 ` Al Viro [this message]
2018-12-24 22:08 ` Jason Gunthorpe
2018-12-24 23:12 ` Jason Gunthorpe
2018-12-25 8:41 ` Gal Pressman
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=20181223165312.GE2217@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=bvanassche@acm.org \
--cc=corbet@lwn.net \
--cc=dledford@redhat.com \
--cc=galpress@amazon.com \
--cc=hch@lst.de \
--cc=jgg@ziepe.ca \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=tariqt@mellanox.com \
--cc=torvalds@linux-foundation.org \
--cc=xavier.huwei@huawei.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 NNTP newsgroup(s).