From: Stanislaw Gruszka <sgruszka@redhat•com>
To: Colin King <colin.king@canonical•com>
Cc: Helmut Schaa <helmut.schaa@googlemail•com>,
Kalle Valo <kvalo@codeaurora•org>,
linux-wireless@vger•kernel.org, netdev@vger•kernel.org,
kernel-janitors@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH] rt2x00: fix spelling mistake in various macros, UKNOWN -> UNKNOWN
Date: Wed, 18 Apr 2018 13:55:22 +0200 [thread overview]
Message-ID: <20180418115521.GA21136@redhat.com> (raw)
In-Reply-To: <20180418114750.1978-1-colin.king@canonical.com>
On Wed, Apr 18, 2018 at 12:47:50PM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical•com>
>
> Rename several macros that contain mispellings of UNKNOWN
>
> Signed-off-by: Colin Ian King <colin.king@canonical•com>
Acked-by: Stanislaw Gruszka <sgruszka@redhat•com>
next prev parent reply other threads:[~2018-04-18 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 11:47 [PATCH] rt2x00: fix spelling mistake in various macros, UKNOWN -> UNKNOWN Colin King
2018-04-18 11:55 ` Stanislaw Gruszka [this message]
2018-04-30 10:35 ` Kalle Valo
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=20180418115521.GA21136@redhat.com \
--to=sgruszka@redhat$(echo .)com \
--cc=colin.king@canonical$(echo .)com \
--cc=helmut.schaa@googlemail$(echo .)com \
--cc=kernel-janitors@vger$(echo .)kernel.org \
--cc=kvalo@codeaurora$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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