From: patchwork-bot+netdevbpf@kernel.org
To: Julia Lawall <julia.lawall@inria.fr>
Cc: linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org,
alsa-devel@alsa-project.org, samba-technical@lists.samba.org,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-scsi@vger.kernel.org, andreyknvl@gmail.com,
linux-usb@vger.kernel.org
Subject: Re: [PATCH 0/6] use kzalloc
Date: Mon, 14 Mar 2022 20:30:11 +0000 [thread overview]
Message-ID: <164728981116.21494.4613160192240776648.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220312102705.71413-1-Julia.Lawall@inria.fr>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 12 Mar 2022 11:26:59 +0100 you wrote:
> Use kzalloc instead of kmalloc + memset.
>
> ---
>
> drivers/net/ethernet/mellanox/mlx4/en_rx.c | 3 +--
> drivers/net/wireless/zydas/zd1201.c | 3 +--
> drivers/scsi/lpfc/lpfc_debugfs.c | 9 ++-------
> drivers/usb/gadget/legacy/raw_gadget.c | 3 +--
> fs/cifs/transport.c | 3 +--
> sound/core/seq/oss/seq_oss_init.c | 3 +--
> 6 files changed, 7 insertions(+), 17 deletions(-)
Here is the summary with links:
- [2/6] net/mlx4_en: use kzalloc
https://git.kernel.org/netdev/net-next/c/3c2dfb735b4a
- [5/6] zd1201: use kzalloc
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-03-14 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 10:26 [PATCH 0/6] use kzalloc Julia Lawall
2022-03-12 10:27 ` [PATCH 4/6] scsi: lpfc: " Julia Lawall
2022-03-12 21:45 ` Joe Perches
2022-03-14 11:34 ` Dan Carpenter
2022-03-14 11:50 ` Julia Lawall
2022-03-14 20:30 ` patchwork-bot+netdevbpf [this message]
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=164728981116.21494.4613160192240776648.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=andreyknvl@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=samba-technical@lists.samba.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