linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Cc: Bluez mailing list <linux-bluetooth@vger.kernel.org>,
	ChromeOS Bluetooth Upstreaming 
	<chromeos-bluetooth-upstreaming@chromium.org>,
	"David S. Miller" <davem@davemloft.net>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	netdev <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH v2 1/1] Bluetooth: Update add_device with wakeable actions
Date: Mon, 6 Apr 2020 20:04:55 +0200	[thread overview]
Message-ID: <DEFFA6AD-01A6-49B7-AB76-4F763A46981D@holtmann.org> (raw)
In-Reply-To: <20200325224500.v2.1.I196e4af9cde6c6e6aa7102906722cb9df8c80a7b@changeid>

Hi Abhishek,

> Add new actions to add_device to allow it to set or unset a device as
> wakeable. When the set wakeable and unset wakeable actions are used, the
> autoconnect property is not updated and the device is not added to the
> whitelist (if BR/EDR).

I am currently preferring to go with Device Flags for this. See my mgmt-api.txt proposal that I just send a few minutes ago.

Regards

Marcel


  reply	other threads:[~2020-04-06 18:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26  5:45 [PATCH v2 0/1] Bluetooth: Add actions to set wakeable in add device Abhishek Pandit-Subedi
2020-03-26  5:45 ` [PATCH v2 1/1] Bluetooth: Update add_device with wakeable actions Abhishek Pandit-Subedi
2020-04-06 18:04   ` Marcel Holtmann [this message]
2020-03-27  2:59 ` [PATCH v2 0/1] Bluetooth: Add actions to set wakeable in add device Abhishek Pandit-Subedi

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=DEFFA6AD-01A6-49B7-AB76-4F763A46981D@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=abhishekpandit@chromium.org \
    --cc=chromeos-bluetooth-upstreaming@chromium.org \
    --cc=davem@davemloft.net \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).