From: Jakub Kicinski <kuba@kernel.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull-request: wireless-drivers-2020-11-23
Date: Tue, 24 Nov 2020 08:08:58 -0800 [thread overview]
Message-ID: <20201124080858.0aa8462b@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <87im9vql7i.fsf@codeaurora.org>
On Tue, 24 Nov 2020 09:15:45 +0200 Kalle Valo wrote:
> Jakub Kicinski <kuba@kernel.org> writes:
>
> > On Mon, 23 Nov 2020 16:10:37 +0000 (UTC) Kalle Valo wrote:
> >> wireless-drivers fixes for v5.10
> >>
> >> First set of fixes for v5.10. One fix for iwlwifi kernel panic, others
> >> less notable.
> >>
> >> rtw88
> >>
> >> * fix a bogus test found by clang
> >>
> >> iwlwifi
> >>
> >> * fix long memory reads causing soft lockup warnings
> >>
> >> * fix kernel panic during Channel Switch Announcement (CSA)
> >>
> >> * other smaller fixes
> >>
> >> MAINTAINERS
> >>
> >> * email address updates
> >
> > Pulled, thanks!
> >
> > Please watch out for missing sign-offs.
>
> I assume you refer to commit 97cc16943f23, sorry about that. Currently
> I'm just manually checking sign-offs and missed this patch. My plan is
> to implement proper checks to my patchwork script so I'll notice these
> before I commit the patch (or pull request), just have not yet find the
> time to do that.
Check out verify_fixes and verify_signoff in Greg's repo:
https://github.com/gregkh/gregkh-linux/tree/master/work
next prev parent reply other threads:[~2020-11-24 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 16:10 pull-request: wireless-drivers-2020-11-23 Kalle Valo
2020-11-23 23:30 ` Jakub Kicinski
2020-11-24 7:15 ` Kalle Valo
2020-11-24 16:08 ` Jakub Kicinski [this message]
2020-11-24 16:38 ` 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=20201124080858.0aa8462b@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).