From: Kalle Valo <kvalo@kernel.org>
To: "Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: "Ajay Singh" <ajay.kathat@microchip.com>,
"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
"Alexis Lothoré" <alexis.lothore@bootlin.com>
Subject: Re: [PATCH 1/2] wifi: wilc1000: set atomic flag on kmemdup in srcu critical section
Date: Tue, 16 Apr 2024 15:31:13 +0000 (UTC) [thread overview]
Message-ID: <171328147120.402909.13178958912833921498.kvalo@kernel.org> (raw)
In-Reply-To: <20240410-wilc_srcu_to_rcu-v1-1-a9ff5b10feaa@bootlin.com>
Alexis Lothoré <alexis.lothore@bootlin.com> wrote:
> In order to prepare wilc1000 driver switch from SRCU to RCU, make sure that
> allocators are provided with the GFP_ATOMIC flag when called in a critical
> read section.
>
> Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
2 patches applied to wireless-next.git, thanks.
35aee01ff43d wifi: wilc1000: set atomic flag on kmemdup in srcu critical section
f236464f1db7 wifi: wilc1000: convert list management to RCU
--
https://patchwork.kernel.org/project/linux-wireless/patch/20240410-wilc_srcu_to_rcu-v1-1-a9ff5b10feaa@bootlin.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-04-16 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 7:10 [PATCH 0/2] wifi: wilc1000: use RCU instead of SRCU Alexis Lothoré
2024-04-10 7:10 ` [PATCH 1/2] wifi: wilc1000: set atomic flag on kmemdup in srcu critical section Alexis Lothoré
2024-04-16 15:31 ` Kalle Valo [this message]
2024-04-10 7:10 ` [PATCH 2/2] wifi: wilc1000: convert list management to RCU Alexis Lothoré
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=171328147120.402909.13178958912833921498.kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=ajay.kathat@microchip.com \
--cc=alexis.lothore@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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 read-only IMAP folder(s) and NNTP newsgroup(s).