Open Source Telephony
 help / color / mirror / Atom feed
From: Nicolas Serafini <nicolas.serafini@sensefly.com>
To: ofono@ofono.org
Subject: Re: [PATCH] mbim: add optional copy of TEMP_FAILURE_RETRY macro (fix musl compile)
Date: Mon, 28 Jan 2019 15:19:56 +0000	[thread overview]
Message-ID: <20190128161950.00004190@sensefly.com> (raw)
In-Reply-To: <99537250-8354-4976-95A4-5EF7362DBBED@holtmann.org>

[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]

On Mon, 28 Jan 2019 13:34:37 +0100 Marcel Holtmann <marcel@holtmann.org> wrote:

Hi Marcel,

>Hi Nicolas,
>
>> TEMP_FAILURE_RETRY is not available on musl.
>> 
>> Signed-off-by: Nicolas Serafini <nicolas.serafini@sensefly.com>
>> ---
>> drivers/mbimmodem/mbim.c | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>> 
>> diff --git a/drivers/mbimmodem/mbim.c b/drivers/mbimmodem/mbim.c
>> index 54b18acf..4b040528 100644
>> --- a/drivers/mbimmodem/mbim.c
>> +++ b/drivers/mbimmodem/mbim.c
>> @@ -37,6 +37,16 @@
>> #include "mbim-message.h"
>> #include "mbim-private.h"
>> 
>> +/* taken from glibc unistd.h for musl support */
>> +#ifndef TEMP_FAILURE_RETRY
>> +#define TEMP_FAILURE_RETRY(expression)             \
>> +  (__extension__                                   \
>> +    ({ long int __result;                          \
>> +       do __result = (long int) (expression);      \
>> +       while (__result == -1L && errno == EINTR);  \
>> +       __result; }))
>> +#endif
>> +
>
>or you use the notation that is used in src/storage.h and maybe even
>move it to a more common place. The TFR macro is used in various
>places.

Yes it's a good idea, what do you think about putting it in the "include/types.h" file.

>
>Regards
>
>Marcel
>

Regards

Nicolas

      reply	other threads:[~2019-01-28 15:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28  9:32 [PATCH] mbim: add optional copy of TEMP_FAILURE_RETRY macro (fix musl compile) Nicolas Serafini
2019-01-28 12:34 ` Marcel Holtmann
2019-01-28 15:19   ` Nicolas Serafini [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=20190128161950.00004190@sensefly.com \
    --to=nicolas.serafini@sensefly.com \
    --cc=ofono@ofono.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