From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>,
Linux BPF <bpf@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Alan Maguire <alan.maguire@oracle.com>,
Ross Zwisler <zwisler@google.com>
Subject: Re: [PATCH v2] Documentation: bpf: Fix link to BTF doc
Date: Tue, 28 Feb 2023 14:48:56 +0700 [thread overview]
Message-ID: <Y/2x6KLsGecrIIok@debian.me> (raw)
In-Reply-To: <7cd545a2-4a5c-1961-1cf7-cd0f24e41df8@iogearbox.net>
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
On Mon, Feb 27, 2023 at 10:11:52PM +0100, Daniel Borkmann wrote:
> Applied, thanks! Looks like kselftest.rst has a similar issue, could you
> send a fix for this too?
>
The fixup is in the recently sent miniseries at [1].
[1]: https://lore.kernel.org/linux-doc/20230228074523.11493-1-bagasdotme@gmail.com/
Thanks!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-02-28 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 8:35 [PATCH v2] Documentation: bpf: Fix link to BTF doc Bagas Sanjaya
2023-02-22 18:55 ` Ross Zwisler
2023-02-23 1:58 ` Bagas Sanjaya
2023-02-27 21:11 ` Daniel Borkmann
2023-02-28 7:48 ` Bagas Sanjaya [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=Y/2x6KLsGecrIIok@debian.me \
--to=bagasdotme@gmail.com \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
--cc=zwisler@google.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.