public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel•org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel•org>
Cc: Tony Luck <tony.luck@intel•com>,
	Anton Vorontsov <anton@enomsg•org>,
	Rob Herring <robh+dt@kernel•org>,
	bpf@vger•kernel.org, Song Liu <songliubraving@fb•com>,
	Martin KaFai Lau <kafai@fb•com>,
	linux-kernel@vger•kernel.org, linux-kselftest@vger•kernel.org,
	linux-riscv@lists•infradead.org, kvm-riscv@lists•infradead.org,
	netdev@vger•kernel.org, linux-gpio@vger•kernel.org,
	linux-samsung-soc@vger•kernel.org, Chen-Yu Tsai <wens@csie•org>,
	KP Singh <kpsingh@kernel•org>,
	John Fastabend <john.fastabend@gmail•com>,
	linux-fsdevel@vger•kernel.org, Anup Patel <anup.patel@wdc•com>,
	Jonathan Corbet <corbet@lwn•net>,
	Bartosz Golaszewski <brgl@bgdev•pl>,
	Shuah Khan <shuah@kernel•org>, Colin Cross <ccross@android•com>,
	Alex Shi <alexs@kernel•org>, Yonghong Song <yhs@fb•com>,
	Kees Cook <keescook@chromium•org>,
	"J. Bruce Fields" <bfields@fieldses•org>,
	kvm@vger•kernel.org, Alexander Viro <viro@zeniv•linux.org.uk>,
	sparmaintainer@unisys•com,
	Linux Doc Mailing List <linux-doc@vger•kernel.org>,
	Atish Patra <atish.patra@wdc•com>,
	devicetree@vger•kernel.org,
	Linus Walleij <linus.walleij@linaro•org>,
	Jeff Layton <jlayton@kernel•org>
Subject: Re: [PATCH v3 00/23] Fix some issues at documentation
Date: Tue, 19 Oct 2021 11:53:33 -0500	[thread overview]
Message-ID: <YW74Dez4/3cIbe1Q@robh.at.kernel.org> (raw)
In-Reply-To: <cover.1634630485.git.mchehab+huawei@kernel.org>

On Tue, 19 Oct 2021 09:03:59 +0100, Mauro Carvalho Chehab wrote:
> Hi Jon,
> 
> This series is against today's next (next-20211019) and addresses missing
> links to Documentation/*.
> 
> The best would be to have the patches applied directly to the trees that
> contain the patches that moved/renamed files, and then apply the
> remaining ones either later during the merge window or just afterwards,
> whatever works best for you.
> 
> Regards,
> Mauro
> 
> Mauro Carvalho Chehab (23):
>   visorbus: fix a copyright symbol that was bad encoded
>   libbpf: update index.rst reference
>   docs: accounting: update delay-accounting.rst reference
>   MAINTAINERS: update arm,vic.yaml reference
>   MAINTAINERS: update aspeed,i2c.yaml reference
>   MAINTAINERS: update faraday,ftrtc010.yaml reference
>   MAINTAINERS: update ti,sci.yaml reference
>   MAINTAINERS: update intel,ixp46x-rng.yaml reference
>   MAINTAINERS: update nxp,imx8-jpeg.yaml reference
>   MAINTAINERS: update gemini.yaml reference
>   MAINTAINERS: update brcm,unimac-mdio.yaml reference
>   MAINTAINERS: update mtd-physmap.yaml reference

Applied patches 3-12.

>   Documentation: update vcpu-requests.rst reference
>   bpftool: update bpftool-cgroup.rst reference
>   docs: translations: zn_CN: irq-affinity.rst: add a missing extension
>   docs: translations: zh_CN: memory-hotplug.rst: fix a typo
>   docs: fs: locks.rst: update comment about mandatory file locking
>   fs: remove a comment pointing to the removed mandatory-locking file
>   Documentation/process: fix a cross reference
>   dt-bindings: mfd: update x-powers,axp152.yaml reference
>   regulator: dt-bindings: update samsung,s2mpa01.yaml reference
>   regulator: dt-bindings: update samsung,s5m8767.yaml reference
>   dt-bindings: reserved-memory: ramoops: update ramoops.yaml references

      parent reply	other threads:[~2021-10-19 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19  8:03 [PATCH v3 00/23] Fix some issues at documentation Mauro Carvalho Chehab
2021-10-19  8:04 ` [PATCH v3 02/23] libbpf: update index.rst reference Mauro Carvalho Chehab
2021-10-19  8:04 ` [PATCH v3 14/23] bpftool: update bpftool-cgroup.rst reference Mauro Carvalho Chehab
2021-10-19  9:35   ` Quentin Monnet
2021-10-19 22:31     ` Alexei Starovoitov
2021-10-20  5:46       ` Mauro Carvalho Chehab
2021-10-19 16:53 ` Rob Herring [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=YW74Dez4/3cIbe1Q@robh.at.kernel.org \
    --to=robh@kernel$(echo .)org \
    --cc=alexs@kernel$(echo .)org \
    --cc=anton@enomsg$(echo .)org \
    --cc=anup.patel@wdc$(echo .)com \
    --cc=atish.patra@wdc$(echo .)com \
    --cc=bfields@fieldses$(echo .)org \
    --cc=bpf@vger$(echo .)kernel.org \
    --cc=brgl@bgdev$(echo .)pl \
    --cc=ccross@android$(echo .)com \
    --cc=corbet@lwn$(echo .)net \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=jlayton@kernel$(echo .)org \
    --cc=john.fastabend@gmail$(echo .)com \
    --cc=kafai@fb$(echo .)com \
    --cc=keescook@chromium$(echo .)org \
    --cc=kpsingh@kernel$(echo .)org \
    --cc=kvm-riscv@lists$(echo .)infradead.org \
    --cc=kvm@vger$(echo .)kernel.org \
    --cc=linus.walleij@linaro$(echo .)org \
    --cc=linux-doc@vger$(echo .)kernel.org \
    --cc=linux-fsdevel@vger$(echo .)kernel.org \
    --cc=linux-gpio@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-kselftest@vger$(echo .)kernel.org \
    --cc=linux-riscv@lists$(echo .)infradead.org \
    --cc=linux-samsung-soc@vger$(echo .)kernel.org \
    --cc=mchehab+huawei@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=robh+dt@kernel$(echo .)org \
    --cc=shuah@kernel$(echo .)org \
    --cc=songliubraving@fb$(echo .)com \
    --cc=sparmaintainer@unisys$(echo .)com \
    --cc=tony.luck@intel$(echo .)com \
    --cc=viro@zeniv$(echo .)linux.org.uk \
    --cc=wens@csie$(echo .)org \
    --cc=yhs@fb$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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