All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Sai Teja Aluvala <quic_saluvala@quicinc.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
	luiz.dentz@gmail.com, mka@chromium.org,
	linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
	quic_hemantg@quicinc.com, quic_bgodavar@quicinc.com,
	quic_rjliao@quicinc.com, quic_hbandi@quicinc.com,
	abhishekpandit@chromium.org, mcchou@chromium.org
Subject: Re: [RESEND v1] Bluetooth: hci_qca: Return wakeup for qca_wakeup
Date: Tue, 31 May 2022 21:20:12 +0000	[thread overview]
Message-ID: <165403201205.25010.12372170867802214338.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1653646543-349-1-git-send-email-quic_saluvala@quicinc.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Fri, 27 May 2022 15:45:43 +0530 you wrote:
> This fixes the return value of qca_wakeup(), since
> .wakeup work inversely with original .prevent_wake.
> 
> Fixes: 4539ca67fe8ed (Bluetooth: Rename driver .prevent_wake to .wakeup)
> Signed-off-by: Sai Teja Aluvala <quic_saluvala@quicinc.com>
> ---
>  drivers/bluetooth/hci_qca.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Here is the summary with links:
  - [RESEND,v1] Bluetooth: hci_qca: Return wakeup for qca_wakeup
    https://git.kernel.org/bluetooth/bluetooth-next/c/9271cf2ecc9a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-05-31 21:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 10:15 [RESEND v1] Bluetooth: hci_qca: Return wakeup for qca_wakeup Sai Teja Aluvala
2022-05-27 11:07 ` [RESEND,v1] " bluez.test.bot
2022-05-31 21:20 ` patchwork-bot+bluetooth [this message]

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=165403201205.25010.12372170867802214338.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=abhishekpandit@chromium.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=mcchou@chromium.org \
    --cc=mka@chromium.org \
    --cc=quic_bgodavar@quicinc.com \
    --cc=quic_hbandi@quicinc.com \
    --cc=quic_hemantg@quicinc.com \
    --cc=quic_rjliao@quicinc.com \
    --cc=quic_saluvala@quicinc.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.