From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Lang Daniel via buildroot <buildroot@buildroot.org>
Cc: Lang Daniel <d.lang@abatec.at>, "marcin@bis.org.pl" <marcin@bis.org.pl>
Subject: Re: [Buildroot] [PATCH 2/2] package/bluez5_utils: fix SysV init script
Date: Sun, 19 Mar 2023 14:51:32 +0100 [thread overview]
Message-ID: <20230319145132.4c349769@windsurf> (raw)
In-Reply-To: <VI1P190MB049333A9311E7A4ECAE13B7A9FBC9@VI1P190MB0493.EURP190.PROD.OUTLOOK.COM>
On Thu, 16 Mar 2023 13:53:14 +0000
Lang Daniel via buildroot <buildroot@buildroot.org> wrote:
> - Use daemon name (bluetoothd) as file name.
> - Script doesn't need to be executable.
>
> Signed-off-by: Daniel Lang <d.lang@abatec.at>
> ---
> package/bluez5_utils/{S40bluetooth => S40bluetoothd} | 0
> package/bluez5_utils/bluez5_utils.mk | 4 ++--
> 2 files changed, 2 insertions(+), 2 deletions(-)
> rename package/bluez5_utils/{S40bluetooth => S40bluetoothd} (100%)
> mode change 100755 => 100644
Applied to master, thanks. I have also updated .checkpackageignore to
no longer ignore the warnings that were caused by S40bluetooth.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-03-19 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 13:53 [Buildroot] [PATCH 2/2] package/bluez5_utils: fix SysV init script Lang Daniel via buildroot
2023-03-19 13:51 ` Thomas Petazzoni via buildroot [this message]
2023-03-20 9:04 ` Peter Korsgaard
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=20230319145132.4c349769@windsurf \
--to=buildroot@buildroot.org \
--cc=d.lang@abatec.at \
--cc=marcin@bis.org.pl \
--cc=thomas.petazzoni@bootlin.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.