netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-kernel@vger.kernel.org, Anup Patel <anup.patel@wdc.com>,
	Atish Patra <atish.patra@wdc.com>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>, Martin KaFai Lau <kafai@fb.com>,
	Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
	bpf@vger.kernel.org, kvm-riscv@lists.infradead.org,
	kvm@vger.kernel.org, linux-riscv@lists.infradead.org,
	netdev@vger.kernel.org
Subject: [PATCH 0/4] Address some bad references to Kernel docs
Date: Tue, 16 Nov 2021 12:11:19 +0000	[thread overview]
Message-ID: <cover.1637064577.git.mchehab+huawei@kernel.org> (raw)

Hi Jon,

It follows 4 patches addressing some issues during the 5.16 Kernel development
cycle that were sent to the MLs but weren't merged yet. 

They apply cleanly on the top of 5.16-rc1.

Regards,

Mauro Carvalho Chehab (4):
  libbpf: update index.rst reference
  docs: accounting: update delay-accounting.rst reference
  Documentation: update vcpu-requests.rst reference
  Documentation/process: fix a cross reference

 Documentation/admin-guide/sysctl/kernel.rst  | 2 +-
 Documentation/bpf/index.rst                  | 2 +-
 Documentation/process/submitting-patches.rst | 4 ++--
 arch/riscv/kvm/vcpu.c                        | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

-- 
2.33.1



             reply	other threads:[~2021-11-16 12:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 12:11 Mauro Carvalho Chehab [this message]
2021-11-16 12:11 ` [PATCH 1/4] libbpf: update index.rst reference Mauro Carvalho Chehab
2021-11-17 13:12 ` [PATCH 0/4] Address some bad references to Kernel docs 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=cover.1637064577.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=anup.patel@wdc.com \
    --cc=atish.patra@wdc.com \
    --cc=bpf@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=kvm-riscv@lists.infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.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 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).