From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Kieran Bingham <kieran.bingham@ideasonboard.com>,
Rui Miguel Silva <rmfrfs@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Martin Kepplinger <martink@posteo.de>,
Purism Kernel Team <kernel@puri.sm>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] media: imx-mipi-csis: csis clock fixes
Date: Wed, 22 Nov 2023 15:22:15 +0200 [thread overview]
Message-ID: <7fc809a2-5eef-47c6-a2ff-24d47f505521@ideasonboard.com> (raw)
In-Reply-To: <CAOMZO5AW0qft5ciGAWuX=RC0zHwAWEpLCyB5TbeE0QH3Nb+nQQ@mail.gmail.com>
On 22/11/2023 15:21, Fabio Estevam wrote:
> Hi Tomi,
>
> On Wed, Nov 22, 2023 at 10:14 AM Tomi Valkeinen
> <tomi.valkeinen@ideasonboard.com> wrote:
>>
>> Two fixes to the csis driver: One to fix remove() another to only enable
>> the clocks when needed.
>>
>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
>> ---
>> Tomi Valkeinen (2):
>> media: imx-mipi-csis: Fix clock handling in remove()
>> media: imx-mipi-csis: Drop extra clock enable at probe()
>
> Shouldn't both patches contain a Fixes tag?
Indeed, yes, I'll add that.
Tomi
next prev parent reply other threads:[~2023-11-22 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 13:13 Tomi Valkeinen
2023-11-22 13:13 ` [PATCH 1/2] media: imx-mipi-csis: Fix clock handling in remove() Tomi Valkeinen
2023-11-22 14:56 ` Laurent Pinchart
2023-11-22 13:13 ` [PATCH 2/2] media: imx-mipi-csis: Drop extra clock enable at probe() Tomi Valkeinen
2023-11-22 15:04 ` Laurent Pinchart
2023-11-22 13:21 ` [PATCH 0/2] media: imx-mipi-csis: csis clock fixes Fabio Estevam
2023-11-22 13:22 ` Tomi Valkeinen [this message]
2023-11-22 13:44 ` Tomi Valkeinen
2023-11-22 15:05 ` Laurent Pinchart
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=7fc809a2-5eef-47c6-a2ff-24d47f505521@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kernel@puri.sm \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=martink@posteo.de \
--cc=mchehab@kernel.org \
--cc=rmfrfs@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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®