From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH 0/4] docs: e100[0] fix build errors Date: Sat, 23 Jun 2018 10:38:08 +0900 (KST) Message-ID: <20180623.103808.1504095881749207713.davem@davemloft.net> References: <20180622003708.31848-1-me@tobin.cc> <5718d34758dd55090dbc73441c3b12c6c5c02ff8.camel@intel.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: me@tobin.cc, corbet@lwn.net, linux-doc@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: jeffrey.t.kirsher@intel.com Return-path: In-Reply-To: <5718d34758dd55090dbc73441c3b12c6c5c02ff8.camel@intel.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org From: Jeff Kirsher Date: Fri, 22 Jun 2018 09:44:00 -0700 > 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/ I've applied this series of fixes to my 'net' tree, thanks everyone.