From: Peng Haitao <penght@cn.fujitsu.com>
To: Akira Takeuchi <takeuchi.akr@jp.panasonic.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] mq_timedreceive: 10-2.c: check timeout error rather than invalid parameter error
Date: Thu, 22 Mar 2012 18:16:46 +0800 [thread overview]
Message-ID: <4F6AFC0E.8090405@cn.fujitsu.com> (raw)
In-Reply-To: <20120322183640.ABAE.38390934@jp.panasonic.com>
Akira Takeuchi said the following on 2012-3-22 17:36:
>>> On the other hand, actually, timeout error should not be returned when message
>>> can be performed immediately.
>>>
>>
>> POSIX spec does not say this, so I think it is not necessary to check timeout error.
>
> Really ? POSIX spec describes as below:
>
> Under no circumstance shall the operation fail with a timeout
> if a message can be removed from the message queue immediately.
>
> http://pubs.opengroup.org/onlinepubs/009604499/functions/mq_receive.html
>
> My reading of this is that timeout error must not be returned
> when message can be performed immediately. What do you think of it ?
>
Yeah.
I am sorry missing it:(
The patch looks good.
--
Best Regards,
Peng
>
> Regards,
> Akira Takeuchi
>
>
>
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-03-22 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 4:23 [LTP] [PATCH] mq_timedreceive: 10-2.c: check timeout error rather than invalid parameter error Akira Takeuchi
2012-03-22 8:19 ` Peng Haitao
2012-03-22 9:36 ` Akira Takeuchi
2012-03-22 10:16 ` Peng Haitao [this message]
2012-03-22 13:06 ` Wanlong Gao
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=4F6AFC0E.8090405@cn.fujitsu.com \
--to=penght@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=takeuchi.akr@jp.panasonic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.