[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <167058301660.16848.3282482071239074275.git-patchwork-notify@kernel.org>
Date: Fri, 09 Dec 2022 10:50:16 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Tejun Heo <tj@...nel.org>
Cc: torvalds@...ux-foundation.org, mingo@...hat.com,
peterz@...radead.org, juri.lelli@...hat.com,
vincent.guittot@...aro.org, dietmar.eggemann@....com,
rostedt@...dmis.org, bsegall@...gle.com, mgorman@...e.de,
bristot@...hat.com, vschneid@...hat.com, ast@...nel.org,
daniel@...earbox.net, andrii@...nel.org, martin.lau@...nel.org,
joshdon@...gle.com, brho@...gle.com, pjt@...gle.com,
derkling@...gle.com, haoluo@...gle.com, dvernet@...a.com,
dschatzberg@...a.com, dskarlat@...cmu.edu, riel@...riel.com,
linux-kernel@...r.kernel.org, bpf@...r.kernel.org,
kernel-team@...a.com
Subject: Re: [PATCH v2 01/31] rhashtable: Allow rhashtable to be used from
irq-safe contexts
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@...emloft.net>:
On Tue, 6 Dec 2022 11:36:32 -1000 you wrote:
> rhashtable currently only does bh-safe synchronization making it impossible
> to use from irq-safe contexts. Switch it to use irq-safe synchronization to
> remove the restriction.
>
> v2: Update the lock functions to return the ulong flags value and unlock
> functions to take the value directly instead of passing around the
> pointer. Suggested by Linus.
>
> [...]
Here is the summary with links:
- [v2,01/31] rhashtable: Allow rhashtable to be used from irq-safe contexts
https://git.kernel.org/netdev/net-next/c/e47877c7aa82
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists