All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: 13145886936@163.com
Cc: "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Bluez mailing list <linux-bluetooth@vger.kernel.org>,
	"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	gushengxian <gushengxian@yulong.com>
Subject: Re: [PATCH] Bluetooth: Fix a spelling mistake
Date: Tue, 15 Jun 2021 15:43:54 +0200	[thread overview]
Message-ID: <12122F14-688A-41B0-ABA7-90CC893005E8@holtmann.org> (raw)
In-Reply-To: <20210615112443.13956-1-13145886936@163.com>

Hi,

> Fix a spelling mistake.
> 
> Signed-off-by: gushengxian <gushengxian@yulong.com>
> ---
> net/bluetooth/hci_conn.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/net/bluetooth/hci_conn.c b/net/bluetooth/hci_conn.c
> index 2b5059a56cda..e91ac6945ec3 100644
> --- a/net/bluetooth/hci_conn.c
> +++ b/net/bluetooth/hci_conn.c
> @@ -760,7 +760,7 @@ void hci_le_conn_failed(struct hci_conn *conn, u8 status)
> 	/* If the status indicates successful cancellation of
> 	 * the attempt (i.e. Unknown Connection Id) there's no point of
> 	 * notifying failure since we'll go back to keep trying to
> -	 * connect. The only exception is explicit connect requests
> +	 * connect. The only exception is explicit connection requests
> 	 * where a timeout + cancel does indicate an actual failure.

I am not even convinced this is a spelling mistake since according to the specification they are connect requests. Anyhow, I no considering patches without proper real name attached to it and send from a total vague email address.

Regards

Marcel


      parent reply	other threads:[~2021-06-15 13:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 11:24 [PATCH] Bluetooth: Fix a spelling mistake 13145886936
2021-06-15 12:02 ` bluez.test.bot
2021-06-15 13:43 ` Marcel Holtmann [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=12122F14-688A-41B0-ABA7-90CC893005E8@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=13145886936@163.com \
    --cc=davem@davemloft.net \
    --cc=gushengxian@yulong.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.