From: Kalle Valo <kvalo@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
linux-wireless@vger.kernel.org, stable@vger.kernel.org,
"Gregory Erwin" <gregerwin256@gmail.com>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
"Eric W . Biederman" <ebiederm@xmission.com>,
vschneid@redhat.com
Subject: Re: [PATCH RESEND v11] hwrng: core - let sleep be interrupted when unregistering hwrng
Date: Wed, 27 Jul 2022 11:44:13 +0300 [thread overview]
Message-ID: <87sfmnosgy.fsf@kernel.org> (raw)
In-Reply-To: <YuD4g+ZPx7uEa999@gondor.apana.org.au> (Herbert Xu's message of "Wed, 27 Jul 2022 16:34:11 +0800")
Herbert Xu <herbert@gondor.apana.org.au> writes:
> On Wed, Jul 27, 2022 at 09:32:20AM +0300, Kalle Valo wrote:
>>
>> But just so that I understand correctly, after Herbert's patch no ath9k
>> changes is needed anymore? That sounds great.
>
> No a small change is still needed in ath9k to completely fix
> the problem, basically a one-liner. Either I could split that
> out and give it to you once the core bits land in mainline, or
> we could just do it in one patch with your ack.
>
> The chances of conflicts are remote.
It's a lot easier to handle that in a single patch via your tree. So
please do CC Toke and linux-wireless when you submit your patch so that
we can then ack it.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-07-27 8:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 21:55 [PATCH RESEND v10] ath9k: let sleep be interrupted when unregistering hwrng Jason A. Donenfeld
2022-07-26 9:44 ` [PATCH RESEND v11] hwrng: core - " Herbert Xu
2022-07-26 10:17 ` Jason A. Donenfeld
2022-07-26 11:32 ` Valentin Schneider
2022-07-27 6:32 ` Kalle Valo
2022-07-27 8:34 ` Herbert Xu
2022-07-27 8:44 ` Kalle Valo [this message]
2022-07-27 8:50 ` Herbert Xu
2022-07-27 9:01 ` Herbert Xu
2022-07-28 10:22 ` [v12 PATCH] " Herbert Xu
2022-07-28 12:39 ` Toke Høiland-Jørgensen
2022-07-28 13:01 ` 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=87sfmnosgy.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ebiederm@xmission.com \
--cc=gregerwin256@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=toke@toke.dk \
--cc=vschneid@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).