linux-kernel - Re: [PATCH 2/2] Documentation: Fix filenames for remoteproc/rpmsg

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAEnQRZC7n127nMaCo+UFnfvKHsRZJTMrmNq4FadfzDJa=1UUnA@mail.gmail.com>
Date: Fri, 14 Nov 2025 13:33:57 +0200
From: Daniel Baluta <daniel.baluta@...il.com>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: Daniel Baluta <daniel.baluta@....com>, corbet@....net, andersson@...nel.org, 
	mathieu.poirier@...aro.org, dan.j.williams@...el.com, cedric.xing@...el.com, 
	pasha.tatashin@...een.com, kevin.tian@...el.com, skhawaja@...gle.com, 
	yesanishhere@...il.com, taimoorzaeem@...il.com, linux@...blig.org, 
	arnaud.pouliquen@...s.st.com, linux-doc@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linux-remoteproc@...r.kernel.org, 
	rdunlap@...radead.org, imx@...ts.linux.dev
Subject: Re: [PATCH 2/2] Documentation: Fix filenames for remoteproc/rpmsg

On Fri, Nov 14, 2025 at 12:29 PM Bagas Sanjaya <bagasdotme@...il.com> wrote:
>
> On Fri, Nov 14, 2025 at 08:57:45AM +0200, Daniel Baluta wrote:
> >    This document describes the rpmsg bus and how to write rpmsg drivers.
> > -  To learn how to add rpmsg support for new platforms, check out remoteproc.txt
> > -  (also a resident of Documentation/).
> > +  To learn how to add rpmsg support for new platforms, check out remoteproc.rst
> > +  (also a resident of Documentation/driver-api).
>
> I think "also a resident of ..." can be dropped, since it's redundant (it's
> already covered in remoteproc.rst cross-reference which transforms into
> the link when you build the docs).

My point here is just to move the patches to a better location without
any crucial modification.
I can send a follow up patch if this is fine with everyone.