From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH v2 BlueZ 3/3] build: Make use of StateDirectory and ConfigurationDirectory
Date: Tue, 19 Apr 2022 11:40:41 -0700 [thread overview]
Message-ID: <CABBYNZJmGGSZbWZ1=aYkAt6yFo=uP_760mHt_-nq8TeYEbRiBg@mail.gmail.com> (raw)
In-Reply-To: <7222b71167dd3ec90d7b4ad1b12b6179cc95f94d.camel@hadess.net>
Hi Bastien,
On Tue, Apr 19, 2022 at 3:33 AM Bastien Nocera <hadess@hadess.net> wrote:
>
> On Fri, 2022-04-15 at 15:30 -0700, Luiz Augusto von Dentz wrote:
> > From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> >
> > This makes use of StateDirectory[1] and ConfigurationDirectory[1] to
> > inform systemd what those paths are used for instead of using
> > ReadWritePaths and ReadOnlyPaths which can lead to issues.
> >
> > Fixes: https://github.com/bluez/bluez/issues/329
>
> FYI, my reviews on those patches are at:
> https://github.com/bluez/bluez/issues/329#issuecomment-1102459104
>
> Cheers
Ive sent a couple of patches addressing them, please have a look.
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2022-04-19 18:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 22:30 [PATCH v2 BlueZ 1/3] storage: Add support for STATE_DIRECTORY environment variable Luiz Augusto von Dentz
2022-04-15 22:30 ` [PATCH v2 BlueZ 2/3] main: Add support for CONFIGURATION_DIRECTORY " Luiz Augusto von Dentz
2022-04-15 22:30 ` [PATCH v2 BlueZ 3/3] build: Make use of StateDirectory and ConfigurationDirectory Luiz Augusto von Dentz
2022-04-19 10:33 ` Bastien Nocera
2022-04-19 18:40 ` Luiz Augusto von Dentz [this message]
2022-04-20 8:54 ` Bastien Nocera
2022-04-16 1:10 ` [v2,BlueZ,1/3] storage: Add support for STATE_DIRECTORY environment variable bluez.test.bot
2022-04-19 0:00 ` [PATCH v2 BlueZ 1/3] " patchwork-bot+bluetooth
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='CABBYNZJmGGSZbWZ1=aYkAt6yFo=uP_760mHt_-nq8TeYEbRiBg@mail.gmail.com' \
--to=luiz.dentz@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.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 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.