From: patchwork-bot+netdevbpf@kernel.org
To: Julia Lawall <julia.lawall@inria.fr>
Cc: linux-scsi@vger.kernel.org, kernel-janitors@vger.kernel.org,
MPT-FusionLinux.pdl@broadcom.com, linux-crypto@vger.kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, alsa-devel@alsa-project.org,
s.shtylyov@omp.ru, linux-ide@vger.kernel.org,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/9] use GFP_KERNEL
Date: Sat, 12 Feb 2022 00:20:10 +0000 [thread overview]
Message-ID: <164462521007.28025.17507178732984421339.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220210204223.104181-1-Julia.Lawall@inria.fr>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 10 Feb 2022 21:42:14 +0100 you wrote:
> Platform_driver and pci_driver probe functions aren't called with
> locks held and thus don't need GFP_ATOMIC. Use GFP_KERNEL instead.
>
> All changes have been compile-tested.
>
> ---
>
> [...]
Here is the summary with links:
- [1/9] net: moxa: use GFP_KERNEL
https://git.kernel.org/netdev/net-next/c/c9ac080b25d9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-02-12 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 20:42 [PATCH 0/9] use GFP_KERNEL Julia Lawall
2022-02-10 20:42 ` [PATCH 8/9] [SCSI] mptfusion: " Julia Lawall
2022-02-11 22:10 ` Martin K. Petersen
2022-02-12 0:20 ` patchwork-bot+netdevbpf [this message]
2022-02-14 12:54 ` (subset) [PATCH 0/9] " Mark Brown
2022-02-15 3:19 ` Martin K. Petersen
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=164462521007.28025.17507178732984421339.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=alsa-devel@alsa-project.org \
--cc=julia.lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
/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