[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4f8b8ce0-727c-4527-b6a5-19f7f035f3c5@xs4all.nl>
Date: Mon, 18 Nov 2024 08:52:31 +0100
From: Hans Verkuil <hverkuil@...all.nl>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH 2/2] docs: media: update location of the media patches
On 18/11/2024 07:09, Mauro Carvalho Chehab wrote:
> Due to recent changes on the way we're maintaining media, the
> location of the main tree was updated.
>
> Change docs accordingly.
>
> Cc: stable@...r.kernel.org
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Reviewed-by: Hans Verkuil <hverkuil@...all.nl>
Regards,
Hans
> ---
> Documentation/admin-guide/media/building.rst | 2 +-
> Documentation/admin-guide/media/saa7134.rst | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/media/building.rst b/Documentation/admin-guide/media/building.rst
> index a06473429916..7a413ba07f93 100644
> --- a/Documentation/admin-guide/media/building.rst
> +++ b/Documentation/admin-guide/media/building.rst
> @@ -15,7 +15,7 @@ Please notice, however, that, if:
>
> you should use the main media development tree ``master`` branch:
>
> - https://git.linuxtv.org/media_tree.git/
> + https://git.linuxtv.org/media.git/
>
> In this case, you may find some useful information at the
> `LinuxTv wiki pages <https://linuxtv.org/wiki>`_:
> diff --git a/Documentation/admin-guide/media/saa7134.rst b/Documentation/admin-guide/media/saa7134.rst
> index 51eae7eb5ab7..18d7cbc897db 100644
> --- a/Documentation/admin-guide/media/saa7134.rst
> +++ b/Documentation/admin-guide/media/saa7134.rst
> @@ -67,7 +67,7 @@ Changes / Fixes
> Please mail to linux-media AT vger.kernel.org unified diffs against
> the linux media git tree:
>
> - https://git.linuxtv.org/media_tree.git/
> + https://git.linuxtv.org/media.git/
>
> This is done by committing a patch at a clone of the git tree and
> submitting the patch using ``git send-email``. Don't forget to
Powered by blists - more mailing lists