All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Tedd Ho-Jeong An <hj.tedd.an@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	Tedd Ho-Jeong An <tedd.an@intel.com>
Subject: Re: [PATCH V2] Bluetooth: hci_vhci: Fix to set the force_wakeup value
Date: Mon, 4 Oct 2021 15:57:15 -0700	[thread overview]
Message-ID: <CABBYNZLcLouiQ_=hE+p_mdZ47fRYzPMU+UsMoOgLih2Pu91VXg@mail.gmail.com> (raw)
In-Reply-To: <20211004170126.206054-1-hj.tedd.an@gmail.com>

Hi Tedd,

On Mon, Oct 4, 2021 at 3:54 PM Tedd Ho-Jeong An <hj.tedd.an@gmail.com> wrote:
>
> From: Tedd Ho-Jeong An <tedd.an@intel.com>
>
> This patch sets the wakeup state of the vhci driver when the
> force_wakeup is updated.
>
> Signed-off-by: Tedd Ho-Jeong An <tedd.an@intel.com>
> ---
>  drivers/bluetooth/hci_vhci.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/drivers/bluetooth/hci_vhci.c b/drivers/bluetooth/hci_vhci.c
> index b45db0db347c..5fd91106e853 100644
> --- a/drivers/bluetooth/hci_vhci.c
> +++ b/drivers/bluetooth/hci_vhci.c
> @@ -176,6 +176,8 @@ static ssize_t force_wakeup_write(struct file *file,
>         if (data->wakeup == enable)
>                 return -EALREADY;
>
> +       data->wakeup = enable;
> +
>         return count;
>  }
>
> --
> 2.25.1

https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=43f51bd946dab69bb38b05863898dd711b7e4506

It already contains this change as well.


-- 
Luiz Augusto von Dentz

  reply	other threads:[~2021-10-04 22:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 17:01 [PATCH V2] Bluetooth: hci_vhci: Fix to set the force_wakeup value Tedd Ho-Jeong An
2021-10-04 22:57 ` Luiz Augusto von Dentz [this message]
2021-10-06  8:57 ` Marcel Holtmann

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='CABBYNZLcLouiQ_=hE+p_mdZ47fRYzPMU+UsMoOgLih2Pu91VXg@mail.gmail.com' \
    --to=luiz.dentz@gmail.com \
    --cc=hj.tedd.an@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=tedd.an@intel.com \
    /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.