From: Yonghong Song <yhs@fb.com>
To: Andrei Matei <andreimatei1@gmail.com>, <bpf@vger.kernel.org>
Subject: Re: [PATCH bpf-next 2/2] selftest/bpf: fix rst formatting in readme
Date: Tue, 24 Nov 2020 11:11:34 -0800 [thread overview]
Message-ID: <b11e8546-a3f1-e135-72f2-3cc7995ad4bf@fb.com> (raw)
In-Reply-To: <20201122022205.57229-2-andreimatei1@gmail.com>
On 11/21/20 6:22 PM, Andrei Matei wrote:
> A couple of places in the readme had invalid rst formatting causing the
> rendering to be off. This patch fixes them with minimal edits.
>
> Signed-off-by: Andrei Matei <andreimatei1@gmail.com>
Acked-by: Yonghong Song <yhs@fb.com>
next prev parent reply other threads:[~2020-11-24 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 2:22 [PATCH bpf-next 1/2] selftest/bpf: fix link in readme Andrei Matei
2020-11-22 2:22 ` [PATCH bpf-next 2/2] selftest/bpf: fix rst formatting " Andrei Matei
2020-11-23 7:22 ` Yonghong Song
2020-11-24 18:29 ` Andrei Matei
2020-11-24 19:09 ` Yonghong Song
2020-11-24 19:11 ` Yonghong Song [this message]
2020-11-24 19:10 ` [PATCH bpf-next 1/2] selftest/bpf: fix link " Yonghong Song
2020-11-24 22:10 ` patchwork-bot+netdevbpf
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=b11e8546-a3f1-e135-72f2-3cc7995ad4bf@fb.com \
--to=yhs@fb.com \
--cc=andreimatei1@gmail.com \
--cc=bpf@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).