Re: [PATCH v4 0/2] Refactoring: expand usage of TFR() macro

2023-01-04 Thread Thomas Huth
On 02/11/2022 21.30, Nikita Ivanov wrote: Hi! Is there any update on this? I haven't received any comments. Sorry, seems like this fell through the cracks since it was not quite clear which maintainer should pick it up. I'll take the patches for my next pull request. Thomas On Sun, Oct 2

Re: [PATCH v4 0/2] Refactoring: expand usage of TFR() macro

2022-11-02 Thread Nikita Ivanov
Hi! Is there any update on this? I haven't received any comments. On Sun, Oct 23, 2022 at 12:04 PM Nikita Ivanov wrote: > At the moment, TFR() macro has a vague name and is not used > where it possibly could be. In order to make it more transparent > and useful, it was decided to refactor it to

[PATCH v4 0/2] Refactoring: expand usage of TFR() macro

2022-10-23 Thread Nikita Ivanov
At the moment, TFR() macro has a vague name and is not used where it possibly could be. In order to make it more transparent and useful, it was decided to refactor it to make it closer to the similar one in glibc: TEMP_FAILURE_RETRY(). Now, macro evaluates into an expression and is named RETRY_ON_E