From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: "Tobin C. Harding" <me@tobin.cc>, Jonathan Corbet <corbet@lwn.net>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] docs: e100[0] fix build errors
Date: Fri, 22 Jun 2018 09:44:00 -0700 [thread overview]
Message-ID: <5718d34758dd55090dbc73441c3b12c6c5c02ff8.camel@intel.com> (raw)
In-Reply-To: <20180622003708.31848-1-me@tobin.cc>
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
On Fri, 2018-06-22 at 10:37 +1000, Tobin C. Harding wrote:
> I may be a little confused here, I'm getting docs build failure on
> Linus' mainline, linux-next, and your docs-next but different errors.
> There seems to be patches to the first two trees that are not in your
> docs-next tree?
>
> Do networking docs typically go through your tree? Looks like
> networking has done some conversion to rst that hasn't gone through
> your
> tree. Or else my git skills are failing.
Networking documentation changes went through David Miller's networking
tree because he maintains changes under Documentation/networking/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-22 16:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 0:37 Tobin C. Harding
2018-06-22 0:37 ` [PATCH 1/4] Documentation: e100: Use correct heading adornment Tobin C. Harding
2018-06-22 16:44 ` Jeff Kirsher
2018-06-22 0:37 ` [PATCH 2/4] Documentation: e1000: " Tobin C. Harding
2018-06-22 16:45 ` Jeff Kirsher
2018-06-22 0:37 ` [PATCH 3/4] Documentation: e100: Fix docs build error Tobin C. Harding
2018-06-22 16:46 ` Jeff Kirsher
2018-06-22 0:37 ` [PATCH 4/4] Documentation: e1000: " Tobin C. Harding
2018-06-22 16:47 ` Jeff Kirsher
2018-06-22 16:44 ` Jeff Kirsher [this message]
2018-06-23 1:38 ` [PATCH 0/4] docs: e100[0] fix build errors David Miller
2018-06-22 20:22 ` Randy Dunlap
2018-06-24 23:41 ` Tobin C. Harding
2018-06-25 1:11 ` Kirsher, Jeffrey T
2018-06-25 2:06 ` Tobin C. Harding
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=5718d34758dd55090dbc73441c3b12c6c5c02ff8.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®