From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Umang Jain <umang.jain@ideasonboard.com>
Cc: Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
kernel-list@raspberrypi.com, Stefan Wahren <wahrenst@gmx.net>
Subject: Re: [PATCH v3 0/2] staging: staging: vchiq_arm: Two memory leak fixes
Date: Wed, 16 Oct 2024 09:58:00 +0200 [thread overview]
Message-ID: <2024101622-upgrade-grape-33c2@gregkh> (raw)
In-Reply-To: <20241014100624.104987-1-umang.jain@ideasonboard.com>
On Mon, Oct 14, 2024 at 03:36:22PM +0530, Umang Jain wrote:
> Two memory leaks were identified and this series addresses those leaks.
>
> Changes in v3:
> - Add Fixes tag to 1/2 as well.
> (Suggestion by Dan Carpenter)
>
> changes in v2:
> - Split patches into two
>
> v1:
> - https://lore.kernel.org/linux-staging/b176520b-5578-40b0-9d68-b1051810c5bb@gmx.net/T/#t
>
> Umang Jain (2):
> staging: vchiq_arm: Utilise devm_kzalloc() for allocation
> staging: vchiq_arm: Utilize devm_kzalloc() for allocation
You have two commits with almost identical commit messages (one with a
spelling mistake.) Please fix this up to have them be unique not in a
way with a misspelling :)
thanks,
greg k-h
prev parent reply other threads:[~2024-10-16 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 10:06 [PATCH v3 0/2] staging: staging: vchiq_arm: Two memory leak fixes Umang Jain
2024-10-14 10:06 ` [PATCH v3 1/2] staging: vchiq_arm: Utilise devm_kzalloc() for allocation Umang Jain
2024-10-14 10:06 ` [PATCH v3 2/2] staging: vchiq_arm: Utilize " Umang Jain
2024-10-14 10:11 ` [PATCH v3 0/2] staging: staging: vchiq_arm: Two memory leak fixes Dan Carpenter
2024-10-16 7:58 ` Greg Kroah-Hartman [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=2024101622-upgrade-grape-33c2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@linaro.org \
--cc=kernel-list@raspberrypi.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=umang.jain@ideasonboard.com \
--cc=wahrenst@gmx.net \
/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 NNTP newsgroup(s).