From: Petr Mladek <pmladek@suse.com>
To: Vincenzo MEZZELA <vincenzo.mezzela@suse.com>
Cc: live-patching@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, jpoimboe@kernel.org,
jikos@kernel.org, mbenes@suse.cz, joe.lawrence@redhat.com,
corbet@lwn.net
Subject: Re: [PATCH v2] docs: livepatch: move text out of code block
Date: Tue, 4 Mar 2025 16:51:00 +0100 [thread overview]
Message-ID: <Z8chZIpQkrp1GZhy@pathway> (raw)
In-Reply-To: <20250227163929.141053-1-vincenzo.mezzela@suse.com>
On Thu 2025-02-27 17:39:29, Vincenzo MEZZELA wrote:
> Part of the documentation text is included in the readelf output code
> block. Hence, split the code block and move the affected text outside.
>
> Signed-off-by: Vincenzo MEZZELA <vincenzo.mezzela@suse.com>
JFYI, the patch has been comitted into livepatching.git,
branch for-6.15/trivial.
Best Regards,
Petr
prev parent reply other threads:[~2025-03-04 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 16:39 [PATCH v2] docs: livepatch: move text out of code block Vincenzo MEZZELA
2025-02-28 2:04 ` Bagas Sanjaya
2025-02-28 14:12 ` Miroslav Benes
2025-03-04 15:51 ` Petr Mladek [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=Z8chZIpQkrp1GZhy@pathway \
--to=pmladek@suse.com \
--cc=corbet@lwn.net \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=vincenzo.mezzela@suse.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 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.