The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, monstr@monstr.eu,
	michal.simek@xilinx.com, git@xilinx.com, stable@kernel.org,
	Sam Bobrowicz <sam@elite-embedded.com>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Steve Longerbeam <slongerbeam@gmail.com>,
	"open list:V4L2 CAMERA SENSOR DRIVERS"
	<linux-media@vger.kernel.org>
Subject: Re: [PATCH v2] media: ov5640: fix get_light_freq on auto
Date: Fri, 13 Dec 2024 11:30:38 +0100	[thread overview]
Message-ID: <05ce02de-6eed-4f28-8052-56ca9cac4b64@amd.com> (raw)
In-Reply-To: <Z1v2VRzgUVpHZvXR@kekkonen.localdomain>

Hi Ailus, +Greg

On 12/13/24 09:54, Sakari Ailus wrote:
> Hi Michal,
> 
> Thanks for the patch.
> 
> On Fri, Nov 22, 2024 at 09:28:01AM +0100, Michal Simek wrote:
>> From: Sam Bobrowicz <sam@elite-embedded.com>
>>
>> Light frequency was not properly returned when in auto
>> mode and the detected frequency was 60Hz.
>>
>> Fixes: 19a81c1426c1 ("[media] add Omnivision OV5640 sensor driver")
>> Signed-off-by: Sam Bobrowicz <sam@elite-embedded.com>
>> Signed-off-by: Michal Simek <michal.simek@amd.com>
>> Cc: <stable@kernel.org>
> 
> Cc: stable@vger.kernel.org
> 
> And right after the Fixes: tag.
> 
> I fixed it this time.

Thanks for this. I was trying to find out if this is described anywhere because 
in stable tree both ways are used. Also Greg's script didn't report any issue 
with it. Is it a rule for media tree or your rule or described somewhere?

I have no problem with that rule but just want to understand where this request 
is coming from.

Thanks,
Michal

  reply	other threads:[~2024-12-13 10:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-22  8:28 [PATCH v2] media: ov5640: fix get_light_freq on auto Michal Simek
2024-12-13  8:54 ` Sakari Ailus
2024-12-13 10:30   ` Michal Simek [this message]
2024-12-13 11:12     ` Greg Kroah-Hartman
2024-12-13 12:37       ` Michal Simek
2024-12-14 18:24       ` Sakari Ailus
2024-12-14 18:41         ` 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=05ce02de-6eed-4f28-8052-56ca9cac4b64@amd.com \
    --to=michal.simek@amd.com \
    --cc=git@xilinx.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hans.verkuil@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=monstr@monstr.eu \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sam@elite-embedded.com \
    --cc=slongerbeam@gmail.com \
    --cc=stable@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