From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Robert Mast <rn.mast@zonnet.nl>
Cc: hdegoede@redhat.com, mchehab@kernel.org,
sakari.ailus@linux.intel.com, linux-media@vger.kernel.org,
linux-staging@lists.linux.dev, andy@kernel.org,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
Robert Mast <rmast@live.nl>
Subject: Re: [PATCH 0/1] media: atomisp: mt9m114: Graceful teardown atomisp and mt9m114
Date: Sat, 18 Apr 2026 14:10:37 +0300 [thread overview]
Message-ID: <20260418111037.GK1824072@killaraus.ideasonboard.com> (raw)
In-Reply-To: <20260418092651.7873-1-rn.mast@zonnet.nl>
Hi Robert,
On Sat, Apr 18, 2026 at 11:26:50AM +0200, Robert Mast wrote:
> From: Robert Mast <rmast@live.nl>
>
> During the many iterations on mt9m114 and atomisp on my T100ta baytrail
> I was annoyed by having to reboot each time, as modprobe -r/modprobe
> wasn't able to fully reinitialize mt9m114 and atomisp, resulting in cpu
> core hang ups. I asked Github Copilot Enterprise to fix it for me, and
> the fix looks quite good and has served me well since. I'm not able to
> distinguish any structural flaw, so please review.
No, sorry. You first need to get a complete understanding of the logic
yourself before you can ask other people to review the code. This
includes cleaning up all the obvious mistakes, and turning it into a
form suitable for upstream. Dumping code isn't acceptable.
This applies to v2 as well.
> Robert Mast (1):
> media: atomisp: mt9m114: Graceful teardown atomisp and mt9m114
>
> drivers/media/i2c/mt9m114.c | 118 ++++++++++++++++--
> .../media/atomisp/pci/atomisp_csi2_bridge.c | 1 +
> .../staging/media/atomisp/pci/atomisp_v4l2.c | 3 +
> 3 files changed, 110 insertions(+), 12 deletions(-)
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2026-04-18 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 9:26 [PATCH 0/1] media: atomisp: mt9m114: Graceful teardown atomisp and mt9m114 Robert Mast
2026-04-18 9:26 ` [PATCH 1/1] " Robert Mast
2026-04-18 9:46 ` Sakari Ailus
2026-04-22 12:09 ` kernel test robot
2026-04-22 14:37 ` kernel test robot
2026-04-18 11:10 ` Laurent Pinchart [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=20260418111037.GK1824072@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=andy@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=rmast@live.nl \
--cc=rn.mast@zonnet.nl \
--cc=sakari.ailus@linux.intel.com \
/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