From: Brandon Brnich <b-brnich@ti.com>
To: Devarsh Thakkar <devarsht@ti.com>, <mchehab@kernel.org>,
<hverkuil@kernel.org>, <benjamin.gaignard@collabora.com>,
<linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <stable@vger.kernel.org>, Nicolas Dufresne <nicolas@ndufresne.ca>
Subject: Re: [PATCH v4 1/4] media: imagination: e5010: Properly Release m2m_dev if probe fails
Date: Mon, 5 Oct 2026 12:33:14 -0500 [thread overview]
Message-ID: <036643d3-c3b1-41ee-9afb-67e4503cf85e@ti.com> (raw)
In-Reply-To: <8afcba70-afb2-4cd0-8bcf-ef20e84744cd@ti.com>
Hi Devarsh
On 10/5/26 8:16 AM, Devarsh Thakkar wrote:
> Hi Brandon,
>
> On 18/09/26 14:38, Devarsh Thakkar wrote:
>> Hi Brandon,
>>
>> Thanks for the patch.
>>
>
> I think this patch [0] is already addressing the same problem.
>
> [0]: https://lore.kernel.org/all/fc08a754-1e0b-42ab-
> ac53-94bff728aef3@ti.com/#r
>
> Since the above patch was posted earlier and hoping the next revision
> for same is coming soon, is it possible for you to drop this patch
> ( media: imagination: e5010: Properly Release m2m_dev if probe fails)
>
> in the next revision for the series?
I can drop, but this patch[0] adds another label as well. I wanted to
fix label issue before that patch so it doesn't propagate a known bug.
It doesn't matter, one of us would just need to rebase our patches.
Since that patch was from April of this year, I can switch to their
authorship and keep signed off by but address the comment you and
Nicolas made and add my own sign off. Does that work or should I just
wait for them to send patch?
Best,
Brandon
[0]: https://lore.kernel.org/all/20260831213231.2125544-3-b-brnich@ti.com/
next prev parent reply other threads:[~2026-10-05 17:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 21:32 [PATCH v4 0/4] E5010 Probe Cleanup and Adding autosuspend Brandon Brnich
2026-08-31 21:32 ` [PATCH v4 1/4] media: imagination: e5010: Properly Release m2m_dev if probe fails Brandon Brnich
2026-09-18 9:08 ` Devarsh Thakkar
2026-10-05 13:16 ` Devarsh Thakkar
2026-10-05 17:33 ` Brandon Brnich [this message]
2026-08-31 21:32 ` [PATCH v4 2/4] media: imagination: e5010: Fix clk never enabled without CONFIG_PM Brandon Brnich
2026-09-18 9:11 ` Devarsh Thakkar
2026-08-31 21:32 ` [PATCH v4 3/4] media: imagination: e5010: Move e5010_init_device to Runtime Resume Hook Brandon Brnich
2026-09-18 9:41 ` Devarsh Thakkar
2026-08-31 21:32 ` [PATCH v4 4/4] media: imagination: e5010: Enable autosuspend for runtime PM Brandon Brnich
2026-09-18 15:55 ` Devarsh Thakkar
2026-09-24 19:25 ` Brandon Brnich
2026-09-28 13:24 ` Devarsh Thakkar
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=036643d3-c3b1-41ee-9afb-67e4503cf85e@ti.com \
--to=b-brnich@ti.com \
--cc=benjamin.gaignard@collabora.com \
--cc=devarsht@ti.com \
--cc=hverkuil@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®