From: Simon Horman <simon.horman@corigine.com>
To: Chenyuan Mi <michenyuan@huawei.com>
Cc: isdn@linux-pingi.de, marcel@holtmann.org,
johan.hedberg@gmail.com, luiz.dentz@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cmtp: fix argument error
Date: Fri, 31 Mar 2023 19:33:57 +0200 [thread overview]
Message-ID: <ZCcZhZXuGXqnIjiZ@corigine.com> (raw)
In-Reply-To: <20230331064520.1320749-1-michenyuan@huawei.com>
On Fri, Mar 31, 2023 at 02:45:20PM +0800, Chenyuan Mi wrote:
> Fix this issue by using BTPROTO_CMTP as argument instead of BTPROTO_HIDP.
Thanks for your patch. Some things you may want to consider:
* I think it would be good to describe what the effect of this problem is,
if it can be observed. And if not, say so. I think it would
also be useful to state how the problem was found. F.e. using a tool, or
by inspection.
* As this is described as a fix, it should probably have a fixes tag.
I think it would be:
Fixes: 8c8de589cedd ("Bluetooth: Added /proc/net/cmtp via bt_procfs_init()")
> Signed-off-by: Chenyuan Mi <michenyuan@huawei.com>
> ---
> net/bluetooth/cmtp/sock.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Code change looks good.
> diff --git a/net/bluetooth/cmtp/sock.c b/net/bluetooth/cmtp/sock.c
> index 96d49d9fae96..cf4370055ce2 100644
> --- a/net/bluetooth/cmtp/sock.c
> +++ b/net/bluetooth/cmtp/sock.c
> @@ -250,7 +250,7 @@ int cmtp_init_sockets(void)
> err = bt_procfs_init(&init_net, "cmtp", &cmtp_sk_list, NULL);
> if (err < 0) {
> BT_ERR("Failed to create CMTP proc file");
> - bt_sock_unregister(BTPROTO_HIDP);
> + bt_sock_unregister(BTPROTO_CMTP);
> goto error;
> }
>
> --
> 2.25.1
next prev parent reply other threads:[~2023-03-31 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 6:45 [PATCH] cmtp: fix argument error Chenyuan Mi
2023-03-31 17:33 ` Simon Horman [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-03 2:35 michenyuan
2023-04-03 9:56 ` Simon Horman
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=ZCcZhZXuGXqnIjiZ@corigine.com \
--to=simon.horman@corigine.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=isdn@linux-pingi.de \
--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=marcel@holtmann.org \
--cc=michenyuan@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).