From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
kernel-list@raspberrypi.com, linux-staging@lists.linux.dev
Subject: Re: [PATCH V2 0/3] staging: vchiq_arm: Fix regression & resource leaks
Date: Tue, 15 Jul 2025 19:44:14 +0200 [thread overview]
Message-ID: <2025071555-stubbed-hardiness-8306@gregkh> (raw)
In-Reply-To: <20250715161108.3411-1-wahrenst@gmx.net>
On Tue, Jul 15, 2025 at 06:11:05PM +0200, Stefan Wahren wrote:
> This small series fixes a regression introduced by recent changes and
> possible resource leaks in the VCHIQ driver.
>
> Changes in V2:
> - Add Maíra's Reviewed-bys
> - Fix Reported address in patch #2
>
> Stefan Wahren (3):
> Revert "staging: vchiq_arm: Improve initial VCHIQ connect"
> Revert "staging: vchiq_arm: Create keep-alive thread during probe"
> staging: vchiq_arm: Make vchiq_shutdown never fail
>
> .../interface/vchiq_arm/vchiq_arm.c | 98 +++++++++++--------
> .../interface/vchiq_arm/vchiq_core.c | 1 -
> .../interface/vchiq_arm/vchiq_core.h | 2 -
> 3 files changed, 56 insertions(+), 45 deletions(-)
I already applied v1, is there any code changes that are different here?
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-15 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 16:11 [PATCH V2 0/3] staging: vchiq_arm: Fix regression & resource leaks Stefan Wahren
2025-07-15 16:11 ` [PATCH V2 1/3] Revert "staging: vchiq_arm: Improve initial VCHIQ connect" Stefan Wahren
2025-07-15 16:11 ` [PATCH V2 2/3] Revert "staging: vchiq_arm: Create keep-alive thread during probe" Stefan Wahren
2025-07-15 16:11 ` [PATCH V2 3/3] staging: vchiq_arm: Make vchiq_shutdown never fail Stefan Wahren
2025-07-15 17:44 ` Greg Kroah-Hartman [this message]
2025-07-15 19:59 ` [PATCH V2 0/3] staging: vchiq_arm: Fix regression & resource leaks Stefan Wahren
2025-07-16 7:33 ` Greg Kroah-Hartman
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=2025071555-stubbed-hardiness-8306@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@linaro.org \
--cc=florian.fainelli@broadcom.com \
--cc=kernel-list@raspberrypi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--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