From: Jonathan Corbet <corbet@lwn.net>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 0/9] Fix references for some missing documentation files
Date: Mon, 2 Jul 2018 11:27:23 -0600 [thread overview]
Message-ID: <20180702112723.654d348c@lwn.net> (raw)
In-Reply-To: <cover.1530005114.git.mchehab+samsung@kernel.org>
On Tue, 26 Jun 2018 06:49:02 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> Having nothing to do while waiting for my plane to arrive while
> returning back from Japan, I ended by writing a small series of
> patches meant to reduce the number of bad Documentation/*
> links that are detected by:
> ./scripts/documentation-file-ref-check
I've applied everything except the two networking patches, since I expect
those to go through Dave's tree.
Thanks,
jon
prev parent reply other threads:[~2018-07-02 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 9:49 [Intel-wired-lan] [PATCH 0/9] Fix references for some missing documentation files Mauro Carvalho Chehab
2018-06-26 9:49 ` [Intel-wired-lan] [PATCH 7/9] networking: e100.rst: Get rid of Sphinx warnings Mauro Carvalho Chehab
2018-06-26 9:49 ` [Intel-wired-lan] [PATCH 8/9] networking: e1000.rst: " Mauro Carvalho Chehab
2018-07-02 17:27 ` Jonathan Corbet [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=20180702112723.654d348c@lwn.net \
--to=corbet@lwn.net \
--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