The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Thorsten Blum <thorsten.blum@toblux.com>
Cc: obitton@habana.ai, ogabbay@kernel.org, ttayar@habana.ai,
	fkassabri@habana.ai, osharabi@habana.ai, dliberman@habana.ai,
	quic_carlv@quicinc.com, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, Koby Elbaz <koby.elbaz@intel.com>,
	Konstantin Sinyuk <konstantin.sinyuk@intel.com>
Subject: Re: [RESEND PATCH] accel/habanalabs/gaudi2: Use kvfree() for memory allocated with kvcalloc()
Date: Sat, 16 Aug 2025 13:02:22 +0200	[thread overview]
Message-ID: <aKBlPnl69z85WblU@wunner.de> (raw)
In-Reply-To: <20240820231028.136126-1-thorsten.blum@toblux.com>

On Wed, Aug 21, 2024 at 01:10:28AM +0200, Thorsten Blum wrote:
> Use kvfree() to fix the following Coccinelle/coccicheck warning reported
> by kfree_mismatch.cocci:
> 
>   WARNING kvmalloc is used to allocate this memory at line 10398
> 
> Reviewed-by: Tomer Tayar <ttayar@habana.ai>
> Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>

Applied to drm-misc-fixes, thanks.

You used toblux.com in the Signed-off-by tag but have since amended
.mailmap to use linux.dev instead.  To avoid a mismatch between the
Signed-off-by tag and the commit author, I've taken the liberty to
hand-edit the former to use linux.dev.

I've also added a Fixes tag and stable designation.

Qianfeng Rong later submitted an identical patch, so I've added a
Reported-by tag to acknowledge that:
https://patch.msgid.link/20250808085530.233737-1-rongqianfeng@vivo.com

Thanks,

Lukas

  reply	other threads:[~2025-08-16 11:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20 23:10 [RESEND PATCH] accel/habanalabs/gaudi2: Use kvfree() for memory allocated with kvcalloc() Thorsten Blum
2025-08-16 11:02 ` Lukas Wunner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-03  7:24 Thorsten Blum
2024-05-31 10:46 Thorsten Blum
2024-05-31 12:22 ` Tomer Tayar

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=aKBlPnl69z85WblU@wunner.de \
    --to=lukas@wunner.de \
    --cc=dliberman@habana.ai \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fkassabri@habana.ai \
    --cc=koby.elbaz@intel.com \
    --cc=konstantin.sinyuk@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=obitton@habana.ai \
    --cc=ogabbay@kernel.org \
    --cc=osharabi@habana.ai \
    --cc=quic_carlv@quicinc.com \
    --cc=thorsten.blum@toblux.com \
    --cc=ttayar@habana.ai \
    /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