From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Clancy Shang <clancy_shang@163.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, zhongjun.yu@quectel.com,
Clancy Shang <clancy.shang@quectel.com>
Subject: Re: [PATCH] Bluetooth: mgmt: Fix wrong param be used
Date: Fri, 5 Jan 2024 09:03:12 +0100 [thread overview]
Message-ID: <1a3a481b-db1f-4325-8ca7-03f2bc44b2a2@molgen.mpg.de> (raw)
In-Reply-To: <20240105031111.132851-1-clancy_shang@163.com>
Dear Clancy,
Thank you for your patch.
Am 05.01.24 um 04:11 schrieb clancy_shang@163.com:
> From: Clancy Shang <clancy.shang@quectel.com>
>
> bluez lib could not receive MGMT_EV_DEVICE_FLAGS_CHANGED notifications
> after sending MGMT_OP_SET_DEVICE_FLAGS
Please add a dot/period at the end of sentences.
Please extend the commit message to describe your fix, and why it fixes
the problem.
> Signed-off-by: Clancy Shang <clancy.shang@quectel.com>
> ---
> net/bluetooth/mgmt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c
> index 9dd815b6603f..c74abdf3618f 100644
> --- a/net/bluetooth/mgmt.c
> +++ b/net/bluetooth/mgmt.c
> @@ -5177,7 +5177,7 @@ static int set_device_flags(struct sock *sk, struct hci_dev *hdev, void *data,
>
> done:
> if (status == MGMT_STATUS_SUCCESS)
> - device_flags_changed(sk, hdev, &cp->addr.bdaddr, cp->addr.type,
> + device_flags_changed(NULL, hdev, &cp->addr.bdaddr, cp->addr.type,
> supported_flags, current_flags);
>
> return mgmt_cmd_complete(sk, hdev->id, MGMT_OP_SET_DEVICE_FLAGS, status,
Kind regards,
Paul
next prev parent reply other threads:[~2024-01-05 8:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 3:11 clancy_shang
2024-01-05 8:03 ` Paul Menzel [this message]
2024-01-05 9:52 clancy_shang
2024-01-10 7:01 clancy_shang
2024-01-18 7:49 clancy_shang
2024-01-25 10:57 clancy_shang
2024-02-29 8:40 clancy_shang
2024-02-29 14:14 ` Luiz Augusto von Dentz
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=1a3a481b-db1f-4325-8ca7-03f2bc44b2a2@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=clancy.shang@quectel.com \
--cc=clancy_shang@163.com \
--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=zhongjun.yu@quectel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®