linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-next@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>
Subject: Re: mmotm 2013-06-27-16-36 uploaded (wait event common)
Date: Thu, 27 Jun 2013 23:06:43 -0700	[thread overview]
Message-ID: <51CD27F3.30104@infradead.org> (raw)
In-Reply-To: <20130627225139.798e7b00.akpm@linux-foundation.org>

On 06/27/13 22:51, Andrew Morton wrote:
> On Thu, 27 Jun 2013 22:30:41 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> 
>> On 06/27/13 16:37, akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2013-06-27-16-36 has been uploaded to
>>>
>>>    http://www.ozlabs.org/~akpm/mmotm/
>>>
>>> mmotm-readme.txt says
>>>
>>> README for mm-of-the-moment:
>>>
>>> http://www.ozlabs.org/~akpm/mmotm/
>>>
>>
>> My builds are littered with hundreds of warnings like this one:
>>
>> drivers/tty/tty_ioctl.c:220:6: warning: the omitted middle operand in ?: will always be 'true', suggest explicit middle operand [-Wparentheses]
>>
>> I guess due to this line from wait_event_common():
>>
>> +		__ret = __wait_no_timeout(tout) ?: (tout) ?: 1;
>>
> 
> Ah, sorry, I missed that.  Had I noticed it, I would have spat it back
> on taste grounds alone, it being unfit for human consumption.
> 
> Something like this?
> 
> --- a/include/linux/wait.h~wait-introduce-wait_event_commonwq-condition-state-timeout-fix
> +++ a/include/linux/wait.h
> @@ -196,7 +196,11 @@ wait_queue_head_t *bit_waitqueue(void *,
>  	for (;;) {							\
>  		prepare_to_wait(&wq, &__wait, state);			\
>  		if (condition) {					\
> -			__ret = __wait_no_timeout(tout) ?: __tout ?: 1;	\
> +			__ret = __wait_no_timeout(tout);		\
> +			if (!__ret)					\
> +				__ret = __tout;				\
> +				if (!__ret)				\
> +					__ret = 1;			\
>  			break;						\
>  		}							\
>  									\
> 
> 

That does reduce the number of warnings, but the wait_event_common() macro
needs similar treatment.  I.e., I am still getting those warnings, just not
quite as many. (down from 2 per source code line to 1 per source code line
which contains some kind of wait...)

-- 
~Randy

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2013-06-28  6:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 23:37 mmotm 2013-06-27-16-36 uploaded akpm
2013-06-27 23:57 ` Stephen Rothwell
2013-06-28  0:32   ` Andrew Morton
2013-06-28  1:09     ` Stephen Rothwell
2013-06-28  5:30 ` mmotm 2013-06-27-16-36 uploaded (wait event common) Randy Dunlap
2013-06-28  5:51   ` Andrew Morton
2013-06-28  6:06     ` Randy Dunlap [this message]
2013-06-28  6:56       ` Stephen Rothwell
2013-06-28 15:38         ` Oleg Nesterov
2013-06-28 17:15           ` Oleg Nesterov
2013-06-29 14:00   ` Valdis.Kletnieks
2013-06-30 18:28     ` Oleg Nesterov

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=51CD27F3.30104@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=oleg@redhat.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).