From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: David Dillow <dave-i1Mk8JYDVaaSihdK6806/g@public.gmane.org>,
Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
Cc: roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH for-next 1/2] IB/core: Fix build warnings
Date: Sun, 3 Nov 2013 10:22:02 +0200 [thread overview]
Message-ID: <527607AA.1010309@mellanox.com> (raw)
In-Reply-To: <1383247739.2110.7.camel-a7a0dvSY7KqLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
On 31/10/2013 21:28, David Dillow wrote:
> We want to know about those comparisons, because they often indicate a
> bug -- either in one's thinking, or in the code they've written.
> Changing attr.state from unsigned to signed is unlikely to ever happen,
> as a massive audit would be needed -- this is not an uncommon pattern in
> the kernel.
I agree with Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-03 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 16:21 [PATCH for-next 0/2] Fix build warnings Or Gerlitz
[not found] ` <1383236511-4337-1-git-send-email-ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-31 16:21 ` [PATCH for-next 1/2] IB/core: " Or Gerlitz
[not found] ` <1383236511-4337-2-git-send-email-ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-31 17:02 ` Bart Van Assche
[not found] ` <52728D2F.4020301-HInyCGIudOg@public.gmane.org>
2013-10-31 19:28 ` David Dillow
[not found] ` <1383247739.2110.7.camel-a7a0dvSY7KqLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2013-11-03 8:22 ` Or Gerlitz [this message]
2013-10-31 17:59 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237388CF3CA4-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-10-31 19:44 ` Or Gerlitz
2013-10-31 16:21 ` [PATCH for-next 2/2] IB/mlx4: " Or Gerlitz
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=527607AA.1010309@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=bvanassche-HInyCGIudOg@public.gmane.org \
--cc=dave-i1Mk8JYDVaaSihdK6806/g@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox