All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Michal Simek <michal.simek@amd.com>,
	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: Sat, 14 Dec 2024 19:41:10 +0100	[thread overview]
Message-ID: <2024121425-ended-coastal-0c46@gregkh> (raw)
In-Reply-To: <Z13NZ0lTeTecuC57@kekkonen.localdomain>

On Sat, Dec 14, 2024 at 06:24:39PM +0000, Sakari Ailus wrote:
> Hi Greg,
> 
> On Fri, Dec 13, 2024 at 12:12:18PM +0100, Greg Kroah-Hartman wrote:
> > On Fri, Dec 13, 2024 at 11:30:38AM +0100, Michal Simek wrote:
> > > 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>
> > 
> > That address is totally acceptable.
> 
> The documentation (Documentation/process/stable-kernel-rules.rst) tells to
> use stable@vger.kernel.org nevertheless (we're not discussing the latter
> option here):
> 
> To have a patch you submit for mainline inclusion later automatically picked up
> for stable trees, add this tag in the sign-off area::
> 
>   Cc: stable@vger.kernel.org
> 
> Use ``Cc: stable@kernel.org`` instead when fixing unpublished vulnerabilities:
> it reduces the chance of accidentally exposing the fix to the public by way of
> 'git send-email', as mails sent to that address are not delivered anywhere.

Yes, either works.  But to keep the "signal" of "hey, look, a security
bug!" down, feel free to use stable@kernel.oorg also everywhere just to
make the bad guys have to do more work :)

thanks,

greg k-h

      reply	other threads:[~2024-12-14 18:41 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
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 [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=2024121425-ended-coastal-0c46@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=git@xilinx.com \
    --cc=hans.verkuil@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=michal.simek@amd.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.