From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH trivial] HID: intel-ish-hid: Spelling s/diconnect/disconnect/
Date: Thu, 24 Oct 2019 09:17:46 -0700 [thread overview]
Message-ID: <bce400a8a2ab1a2ddfc1d270fdff2172884696eb.camel@linux.intel.com> (raw)
In-Reply-To: <20191024151837.29421-1-geert+renesas@glider.be>
On Thu, 2019-10-24 at 17:18 +0200, Geert Uytterhoeven wrote:
> Fix misspelling of "disconnect".
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
> drivers/hid/intel-ish-hid/ishtp/hbm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/hid/intel-ish-hid/ishtp/hbm.c
> b/drivers/hid/intel-ish-hid/ishtp/hbm.c
> index c6c9ac09dac3a377..30a91d068306a000 100644
> --- a/drivers/hid/intel-ish-hid/ishtp/hbm.c
> +++ b/drivers/hid/intel-ish-hid/ishtp/hbm.c
> @@ -402,7 +402,7 @@ static void ishtp_hbm_cl_connect_res(struct
> ishtp_device *dev,
> * @dev: ISHTP device instance
> * @disconnect_req: disconnect request structure
> *
> - * Disconnect request bus message from the fw. Send diconnect
> response.
> + * Disconnect request bus message from the fw. Send disconnect
> response.
> */
> static void ishtp_hbm_fw_disconnect_req(struct ishtp_device *dev,
> struct hbm_client_connect_request *disconnect_req)
next prev parent reply other threads:[~2019-10-24 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 15:18 [PATCH trivial] HID: intel-ish-hid: Spelling s/diconnect/disconnect/ Geert Uytterhoeven
2019-10-24 16:17 ` Srinivas Pandruvada [this message]
2019-11-02 20:09 ` Jiri Kosina
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=bce400a8a2ab1a2ddfc1d270fdff2172884696eb.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=geert+renesas@glider.be \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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.