From: Hans de Goede <hdegoede@redhat.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: linux-media@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Kate Hsuan <hpa@redhat.com>
Subject: Re: [PATCH 1/1] media: v4l: subdev: Make link validation safer
Date: Thu, 9 Mar 2023 14:05:40 +0100 [thread overview]
Message-ID: <5e6671be-eb91-599e-7362-b33911141e2a@redhat.com> (raw)
In-Reply-To: <ZAnYY32TyVKyaKhb@kekkonen.localdomain>
Hi,
On 3/9/23 14:00, Sakari Ailus wrote:
> On Thu, Mar 09, 2023 at 02:57:52PM +0200, Tomi Valkeinen wrote:
>> On 09/03/2023 14:56, Sakari Ailus wrote:
>>> On Thu, Mar 09, 2023 at 01:43:50PM +0100, Hans de Goede wrote:
>>>> Hi Sakari,
>>>>
>>>> On 3/9/23 13:27, Sakari Ailus wrote:
>>>>> Link validation currently accesses invalid pointers if the link passed to it
>>>>> is not between two sub-devices. This is of course a driver bug.
>>>>>
>>>>> Ignore the error but print a debug message, as this is how it used to work
>>>>> previously.
>>>>>
>>>>> Fixes: a6b995ed03ff ("media: subdev: use streams in v4l2_subdev_link_validate()")
>>>>> Reported-by: Hans de Goede <hdegoede@redhat.com>
>>>>> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
>>>>> Reported-and-tested-by: Hans de Goede <hdegoede@redhat.com>
>>>>
>>>> FWIW you have my Reported-by in there twice now ...
>>>
>>> Ah, thanks. I'll drop the first tag.
>>
>> $ git grep Reported-and-tested-by Documentation/
>> Documentation/process/maintainer-tip.rst:Please do not use combined tags, e.g. ``Reported-and-tested-by``, as
>
> Uh-oh. Well, I'll just split that. Thanks.
This is new to me too, but good to know. I'll try to get rid of the habbit
of using the combined tags then.
Regards,
Hans
next prev parent reply other threads:[~2023-03-09 13:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 12:27 [PATCH 1/1] media: v4l: subdev: Make link validation safer Sakari Ailus
2023-03-09 12:34 ` Tomi Valkeinen
2023-03-09 12:35 ` Sakari Ailus
2023-03-09 12:34 ` Sakari Ailus
2023-03-09 12:43 ` Hans de Goede
2023-03-09 12:56 ` Sakari Ailus
2023-03-09 12:57 ` Tomi Valkeinen
2023-03-09 13:00 ` Sakari Ailus
2023-03-09 13:05 ` Hans de Goede [this message]
2023-03-12 13:01 ` Laurent Pinchart
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 22:04 IPU3 cameras not working with latest kernel code ? Hans de Goede
2023-03-02 20:22 ` [PATCH 1/1] media: v4l: subdev: Make link validation safer Sakari Ailus
2023-03-03 8:41 ` Tomi Valkeinen
2023-03-03 11:30 ` Sakari Ailus
2023-03-03 11:36 ` Tomi Valkeinen
2023-03-03 15:06 ` Hans de Goede
2023-03-03 17:18 ` Sakari Ailus
2023-03-09 12:09 ` Hans de Goede
2023-03-09 12:28 ` 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=5e6671be-eb91-599e-7362-b33911141e2a@redhat.com \
--to=hdegoede@redhat.com \
--cc=hpa@redhat.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.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