From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: "André Apitzsch" <git@apitzsch.eu>
Cc: linux-media@vger.kernel.org, Ricardo Ribalda <ribalda@kernel.org>
Subject: Re: [PATCH 0/2] Fix PM on imx214 error paths
Date: Wed, 22 Jan 2025 12:04:20 +0000 [thread overview]
Message-ID: <Z5DexPyuveWLzlJm@kekkonen.localdomain> (raw)
In-Reply-To: <2eca7df04384f81372c30f6711871a53d8063174.camel@apitzsch.eu>
Hi André,
On Mon, Jan 20, 2025 at 08:57:39PM +0100, André Apitzsch wrote:
> Hi Sakari,
>
> Am Donnerstag, dem 16.01.2025 um 13:46 +0200 schrieb Sakari Ailus:
> > Hi André,
> >
> > I'm posting this separately as it seems to be backportable, your set
> > needs to go on the top. I've pushed that to my "devel" branch in my
> > git.linuxtv.org tree
> > <URL:https://git.linuxtv.org/sailus/media_tree.git/>,
> > please let me know if you see problems.
>
> The patches look good to me. I don't see any problems, but I haven't
> tested the error paths. That's why no "Tested-by".
>
> Acked-by: André Apitzsch <git@apitzsch.eu>
>
> Shall I send a new version of my patches rebased on yours or can my
> patches be taken from your "devel" branch?
If you're fine with the result of my rebase, there's no need to.
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2025-01-22 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 11:46 [PATCH 0/2] Fix PM on imx214 error paths Sakari Ailus
2025-01-16 11:46 ` [PATCH 1/2] Revert "media: imx214: Fix the error handling in imx214_probe()" Sakari Ailus
2025-01-16 11:47 ` [PATCH 2/2] media: i2c: imx214: Rectify probe error handling related to runtime PM Sakari Ailus
2025-01-20 19:57 ` [PATCH 0/2] Fix PM on imx214 error paths André Apitzsch
2025-01-22 12:04 ` Sakari Ailus [this message]
2025-01-22 21:00 ` André Apitzsch
2025-01-23 7:44 ` Sakari Ailus
2025-02-05 22:17 ` André Apitzsch
2025-02-05 23:26 ` Sakari Ailus
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=Z5DexPyuveWLzlJm@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=git@apitzsch.eu \
--cc=linux-media@vger.kernel.org \
--cc=ribalda@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