diff options
| author | Colin Ian King <colin.king@canonical.com> | 2021-06-01 11:28:55 +0100 |
|---|---|---|
| committer | Kalle Valo <kvalo@codeaurora.org> | 2021-06-03 12:31:53 +0300 |
| commit | fef1cdbba4d12fb67555364c22cc8d7c500600aa (patch) | |
| tree | e98038953275da1b09590f685931296f6c317bc4 | |
| parent | d1dbaa54191e0014493cb4065aadb6764b404dd1 (diff) | |
b43legacy: Fix spelling mistake "overflew" -> "overflowed"
There is a spelling mistake in a comment. Fix it.
Signed-off-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Link: https://lore.kernel.org/r/20210601102855.8884-1-colin.king@canonical.com
| -rw-r--r-- | drivers/net/wireless/broadcom/b43legacy/main.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/net/wireless/broadcom/b43legacy/main.c b/drivers/net/wireless/broadcom/b43legacy/main.c index f64ebff68308..eec3af9c3745 100644 --- a/drivers/net/wireless/broadcom/b43legacy/main.c +++ b/drivers/net/wireless/broadcom/b43legacy/main.c @@ -391,7 +391,7 @@ void b43legacy_tsf_read(struct b43legacy_wldev *dev, u64 *tsf) * registers, we should take care of register overflows. * In theory, the whole tsf read process should be atomic. * We try to be atomic here, by restaring the read process, - * if any of the high registers changed (overflew). + * if any of the high registers changed (overflowed). */ if (dev->dev->id.revision >= 3) { u32 low; |