Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <a677f489aa1c0d1c6723761b521d5f65b5d89401.camel@hadess.net>
Subject: Re: [PATCH BlueZ v7 6/6] adapter: Remove experimental flag for
 PowerState
From:   Bastien Nocera <hadess@hadess.net>
To:     Jonas =?ISO-8859-1?Q?Dre=DFler?= <jonas@dressler.it>,
        linux-bluetooth@vger.kernel.org, luiz.von.dentz@intel.com
Date:   Thu, 17 Nov 2022 15:18:59 +0100
In-Reply-To: <02bf340b-c908-6ee8-ca78-4203b965f3b5@dressler.it>
References: <20220901110719.176944-1-hadess@hadess.net>
         <20220901110719.176944-6-hadess@hadess.net>
         <02bf340b-c908-6ee8-ca78-4203b965f3b5@dressler.it>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
User-Agent: Evolution 3.46.0 (3.46.0-2.fc37) 
MIME-Version: 1.0
Precedence: bulk

On Sun, 2022-11-13 at 16:54 +0100, Jonas Dreßler wrote:
> Hi everyone,
> 
> Can we please apply this one, too? The property being experimental
> means distros
> need to downstream patch BlueZ for the feature to work, I'm not sure
> all packagers
> are aware of that.

I enabled it without the experimental flag in Fedora, because I wrote
it, and I know I'll be responsible for it should there be any bugs.

I really don't want to be on the spot for fixing a problem upstream, or
in another distribution if another distribution enables the feature
without testing it, or responsible for fixing their libraries should we
decide that the API isn't good enough.

> FWIW, I can confirm the feature in gnome-shell works after removing
> the flag!