public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn•net>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel•org>
Cc: Mark Rutland <mark.rutland@arm•com>,
	James Morris <james.morris@microsoft•com>,
	kvm@vger•kernel.org,
	Linux Doc Mailing List <linux-doc@vger•kernel.org>,
	virtualization@lists•linux-foundation.org,
	linux-leds@vger•kernel.org, linux-scsi@vger•kernel.org,
	Ingo Molnar <mingo@redhat•com>,
	intel-wired-lan@lists•osuosl.org,
	Jeff Kirsher <jeffrey.t.kirsher@intel•com>,
	linux-input@vger•kernel.org, devicetree@vger•kernel.org,
	Steven Rostedt <rostedt@goodmis•org>,
	Mauro Carvalho Chehab <mchehab@infradead•org>,
	linux-gpio@vger•kernel.org,
	Jacek Anaszewski <jacek.anaszewski@gmail•com>,
	Andy Whitcroft <apw@canonical•com>,
	netdev@vger•kernel.org, linux-kernel@vger•kernel.org,
	Changbin Du <changbin.du@intel•com>,
	Masami Hiramatsu <mhiramat@kernel•org>,
	linux-kernel@zh-kernel•org, Joe Perches <joe@perches•com>,
	Andrew Morton <akpm@linux-foundation•org>,
	linuxppc-dev@lists•ozlabs.org, "
Subject: Re: [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

      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 [PATCH 0/9] Fix references for some missing documentation files Mauro Carvalho Chehab
2018-06-26  9:49 ` [PATCH 7/9] networking: e100.rst: Get rid of Sphinx warnings Mauro Carvalho Chehab
2018-06-26  9:49 ` [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$(echo .)net \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=apw@canonical$(echo .)com \
    --cc=changbin.du@intel$(echo .)com \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=intel-wired-lan@lists$(echo .)osuosl.org \
    --cc=jacek.anaszewski@gmail$(echo .)com \
    --cc=james.morris@microsoft$(echo .)com \
    --cc=jeffrey.t.kirsher@intel$(echo .)com \
    --cc=joe@perches$(echo .)com \
    --cc=kvm@vger$(echo .)kernel.org \
    --cc=linux-doc@vger$(echo .)kernel.org \
    --cc=linux-gpio@vger$(echo .)kernel.org \
    --cc=linux-input@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-kernel@zh-kernel$(echo .)org \
    --cc=linux-leds@vger$(echo .)kernel.org \
    --cc=linux-scsi@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mark.rutland@arm$(echo .)com \
    --cc=mchehab+samsung@kernel$(echo .)org \
    --cc=mchehab@infradead$(echo .)org \
    --cc=mhiramat@kernel$(echo .)org \
    --cc=mingo@redhat$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=rostedt@goodmis$(echo .)org \
    --cc=virtualization@lists$(echo .)linux-foundation.org \
    /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