From: Kalle Valo <kvalo@kernel.org>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Dmitry Antipov <dmantipov@yandex.ru>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wifi: ath9k: convert msecs to jiffies where needed
Date: Wed, 14 Jun 2023 17:21:58 +0300 [thread overview]
Message-ID: <878rcmf7jt.fsf@kernel.org> (raw)
In-Reply-To: <87a5x2l1bt.fsf@toke.dk> ("Toke \=\?utf-8\?Q\?H\=C3\=B8iland-J\?\= \=\?utf-8\?Q\?\=C3\=B8rgensen\=22's\?\= message of "Wed, 14 Jun 2023 13:39:50 +0200")
Toke Høiland-Jørgensen <toke@toke.dk> writes:
> Kalle Valo <kvalo@kernel.org> writes:
>
>> Toke Høiland-Jørgensen <toke@toke.dk> writes:
>>
>>> Dmitry Antipov <dmantipov@yandex.ru> writes:
>>>
>>>> Since 'ieee80211_queue_delayed_work()' expects timeout in
>>>> jiffies and not milliseconds, 'msecs_to_jiffies()' should
>>>> be used in 'ath_restart_work()' and '__ath9k_flush()'.
>>>>
>>>> Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
>>>
>>> I believe this warrants a:
>>>
>>> Fixes: d63ffc45c5d3 ("ath9k: rename tx_complete_work to hw_check_work")
>>
>> I can add that.
>
> I was hoping you'd say that - thanks :)
BTW you can always assume that I can change or fix the commit messages.
Just let me know exactly what to change, being able to copy paste is
best :)
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-06-14 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 13:46 [PATCH] wifi: ath9k: convert msecs to jiffies where needed Dmitry Antipov
2023-06-13 18:15 ` Toke Høiland-Jørgensen
2023-06-14 5:14 ` Kalle Valo
2023-06-14 11:39 ` Toke Høiland-Jørgensen
2023-06-14 14:21 ` Kalle Valo [this message]
2023-06-15 12:26 ` Toke Høiland-Jørgensen
2023-06-21 18:07 ` 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=878rcmf7jt.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=linux-wireless@vger.kernel.org \
--cc=toke@toke.dk \
/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).