From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 65C28C433FE for ; Thu, 17 Nov 2022 14:19:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240313AbiKQOTG convert rfc822-to-8bit (ORCPT ); Thu, 17 Nov 2022 09:19:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49858 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240327AbiKQOTF (ORCPT ); Thu, 17 Nov 2022 09:19:05 -0500 Received: from relay1-d.mail.gandi.net (relay1-d.mail.gandi.net [217.70.183.193]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D0A67640F for ; Thu, 17 Nov 2022 06:19:02 -0800 (PST) Received: (Authenticated sender: hadess@hadess.net) by mail.gandi.net (Postfix) with ESMTPSA id E269B240003; Thu, 17 Nov 2022 14:18:59 +0000 (UTC) Message-ID: Subject: Re: [PATCH BlueZ v7 6/6] adapter: Remove experimental flag for PowerState From: Bastien Nocera To: Jonas =?ISO-8859-1?Q?Dre=DFler?= , 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 List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org 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!