From: Kalle Valo <kvalo@codeaurora.org>
To: Matteo Croce <mcroce@redhat.com>
Cc: linux-wireless@vger.kernel.org, brcm80211-dev-list@cypress.com,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [PATCH] brcmfmac: fix typos
Date: Fri, 8 Feb 2019 15:27:12 +0000 (UTC) [thread overview]
Message-ID: <20190208152712.EA8CF60F36@smtp.codeaurora.org> (raw)
In-Reply-To: <20190129174717.30566-1-mcroce@redhat.com>
Matteo Croce <mcroce@redhat.com> wrote:
> Fix spelling mistakes in brcmfmac: "lenght" -> "length".
> The typos are also in the special comment blocks which
> translates to documentation.
>
> Signed-off-by: Matteo Croce <mcroce@redhat.com>
Patch applied to wireless-drivers-next.git, thanks.
2359dd09f981 brcmfmac: fix typos
--
https://patchwork.kernel.org/patch/10786663/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2019-02-08 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 17:47 [PATCH] brcm80211: fix typos Matteo Croce
2019-02-08 15:27 ` Kalle Valo [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=20190208152712.EA8CF60F36@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcroce@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).