[PATCH] shared: define MAX_INPUT for musl

[PATCH] shared: define MAX_INPUT for musl

[Sam James]

musl systems don't have MAX_INPUT. Just define it to _POSIX_MAX_INPUT which
musl does have if it's not already defined.

Note that on glibc, the values match anyway (as of glibc-2.36), and indeed
POSIX_MAX_INPUT has the same value on musl too.

Bug: https://bugs.gentoo.org/888467
Signed-off-by: Sam James <sam@gentoo.org>
---
 src/shared/util.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/src/shared/util.c b/src/shared/util.c
index 2f0ae0e86..b466fb001 100644
--- a/src/shared/util.c
+++ b/src/shared/util.c
@@ -28,6 +28,11 @@
 #include <sys/random.h>
 #endif
 
+/* define MAX_INPUT for musl */
+#ifndef MAX_INPUT
+#define MAX_INPUT _POSIX_MAX_INPUT
+#endif
+
 #include "src/shared/util.h"
 
 void *util_malloc(size_t size)
-- 
2.39.1

RE: shared: define MAX_INPUT for musl

[bluez.test.bot]

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

This is automated email and please do not reply to this email!

Dear submitter,

Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=717213

---Test result---

Test Summary:
CheckPatch                    PASS      1.28 seconds
GitLint                       PASS      0.40 seconds
BuildEll                      PASS      32.60 seconds
BluezMake                     PASS      930.49 seconds
MakeCheck                     PASS      12.57 seconds
MakeDistcheck                 PASS      172.91 seconds
CheckValgrind                 PASS      287.70 seconds
CheckSmatch                   PASS      375.44 seconds
bluezmakeextell               PASS      111.96 seconds
IncrementalBuild              PASS      749.42 seconds
ScanBuild                     PASS      1142.01 seconds



---
Regards,
Linux Bluetooth

Re: [PATCH] shared: define MAX_INPUT for musl

[patchwork-bot+bluetooth]

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue, 31 Jan 2023 05:52:58 +0000 you wrote:
> musl systems don't have MAX_INPUT. Just define it to _POSIX_MAX_INPUT which
> musl does have if it's not already defined.
> 
> Note that on glibc, the values match anyway (as of glibc-2.36), and indeed
> POSIX_MAX_INPUT has the same value on musl too.
> 
> Bug: https://bugs.gentoo.org/888467
> Signed-off-by: Sam James <sam@gentoo.org>
> 
> [...]

Here is the summary with links:
  - shared: define MAX_INPUT for musl
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ca6546fe5213

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html