netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Alain Michaud <alainm@chromium.org>,
	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: [RFC PATCH v3 1/5] Bluetooth: Add mgmt op set_wake_capable
Date: Mon, 2 Mar 2020 23:17:33 +0100	[thread overview]
Message-ID: <3532949B-483D-4087-A94B-E9567878EC3E@holtmann.org> (raw)
In-Reply-To: <CANFp7mUehaCSR2W3mXpq2s80YLJVfO2U8D_N+sRzJ2pMZQw1UA@mail.gmail.com>

Hi Abhishek,

> I seem to have forgotten to update the series changes here. In series
> 3, I added a wakeable property to le_conn_param so that the wakeable
> list is only used for BR/EDR as requested in the previous revision.

are you sending a v4?

Regards

Marcel


  reply	other threads:[~2020-03-02 22:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25  0:00 [RFC PATCH v3 0/5] Bluetooth: Handle system suspend gracefully Abhishek Pandit-Subedi
2020-02-25  0:00 ` [RFC PATCH v3 1/5] Bluetooth: Add mgmt op set_wake_capable Abhishek Pandit-Subedi
2020-02-25  1:34   ` Abhishek Pandit-Subedi
2020-03-02 22:17     ` Marcel Holtmann [this message]
2020-03-04  1:11       ` Abhishek Pandit-Subedi
2020-02-25  0:00 ` [RFC PATCH v3 2/5] Bluetooth: Handle PM_SUSPEND_PREPARE and PM_POST_SUSPEND Abhishek Pandit-Subedi
2020-02-25  0:00 ` [RFC PATCH v3 3/5] Bluetooth: Handle BR/EDR devices during suspend Abhishek Pandit-Subedi
2020-02-25  0:00 ` [RFC PATCH v3 4/5] Bluetooth: Handle LE " Abhishek Pandit-Subedi
2020-02-25  0:00 ` [RFC PATCH v3 5/5] Bluetooth: Pause discovery and advertising " 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=3532949B-483D-4087-A94B-E9567878EC3E@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=abhishekpandit@chromium.org \
    --cc=alainm@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=luiz.dentz@gmail.com \
    --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).