From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 0/8] Replace some bad characters on documents
Date: Wed, 16 Jun 2021 08:55:06 +0200 [thread overview]
Message-ID: <cover.1623826294.git.mchehab+huawei@kernel.org> (raw)
Hi Jon,
This series contain the remaining 8 patches I submitted at v3 that
weren't merged yet at -next.
This series is rebased on the top of your docs-next branch.
No changes here, except by some Reviewed/ack lines, and at the
name of the final patch (per PCI maintainer's request).
Mauro Carvalho Chehab (8):
docs: admin-guide: reporting-issues.rst: replace some characters
docs: trace: coresight: coresight-etm4x-reference.rst: replace some
characters
docs: driver-api: ioctl.rst: replace some characters
docs: usb: replace some characters
docs: vm: zswap.rst: replace some characters
docs: filesystems: ext4: blockgroup.rst: replace some characters
docs: networking: device_drivers: replace some characters
docs: PCI: Replace non-breaking spaces to avoid PDF issues
Documentation/PCI/acpi-info.rst | 18 +++++++++---------
Documentation/admin-guide/reporting-issues.rst | 2 +-
Documentation/driver-api/ioctl.rst | 8 ++++----
Documentation/filesystems/ext4/blockgroup.rst | 2 +-
.../device_drivers/ethernet/intel/i40e.rst | 6 +++---
.../device_drivers/ethernet/intel/iavf.rst | 2 +-
.../coresight/coresight-etm4x-reference.rst | 2 +-
Documentation/usb/ehci.rst | 2 +-
Documentation/usb/gadget_printer.rst | 2 +-
Documentation/vm/zswap.rst | 4 ++--
10 files changed, 24 insertions(+), 24 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-16 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 6:55 Mauro Carvalho Chehab [this message]
2021-06-16 6:55 ` [Intel-wired-lan] [PATCH 7/8] docs: networking: device_drivers: replace some characters Mauro Carvalho Chehab
2021-06-17 19:35 ` [Intel-wired-lan] [PATCH 0/8] Replace some bad characters on documents 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.1623826294.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=intel-wired-lan@osuosl.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