public inbox for linux-trace-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriele Monaco <gmonaco@redhat.com>
To: Matteo Martelli <matteo.martelli@codethink.co.uk>,
	rdunlap@infradead.org,  Steven Rostedt <rostedt@goodmis.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-trace-kernel@vger.kernel.org,  linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: skhan@linuxfoundation.org
Subject: Re: [PATCH v2] Documentation/rv: Replace stale website link
Date: Tue, 28 Apr 2026 11:39:02 +0200	[thread overview]
Message-ID: <b4a0f46f1b04462409b61f240aafbcaf6603c5a4.camel@redhat.com> (raw)
In-Reply-To: <d0a66f985640388ab13fda6f7d66c5ad@codethink.co.uk>

Hi Matteo,

On Tue, 2026-04-28 at 11:11 +0200, Matteo Martelli wrote:
> Thanks for addressing this. FWIW this looks good to me, however I've
> just noticed that the same article is also referenced in
> rv/runtime-verification.rst with a slightly different format and no
> link. I think that it might be more clear if we had a References
> section in rv/runtime-verification.rst, add links to publicly
> available articles, and then let the other pages point to that
> section when needed instead of duplicating the references like in
> this case. But that could probably be addressed as a further clean-up
> patch.
> 
> Acked-by: Matteo Martelli <matteo.martelli@codethink.co.uk>
> Tested-by: Matteo Martelli <matteo.martelli@codethink.co.uk>

Thanks for the ack!

That's a good point, I agree it's better to go ahead with this small
patch and I can make a deeper documentation cleanup later.

Thanks,
Gabriele


  reply	other threads:[~2026-04-28  9:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 13:17 [PATCH v2] Documentation/rv: Replace stale website link Gabriele Monaco
2026-04-27 16:50 ` Randy Dunlap
2026-04-28  7:06   ` Gabriele Monaco
2026-04-28  7:16     ` Randy Dunlap
2026-04-28  9:11 ` Matteo Martelli
2026-04-28  9:39   ` Gabriele Monaco [this message]
2026-05-03 15:11 ` Jonathan Corbet

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=b4a0f46f1b04462409b61f240aafbcaf6603c5a4.camel@redhat.com \
    --to=gmonaco@redhat.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=matteo.martelli@codethink.co.uk \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=skhan@linuxfoundation.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