[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180623.103808.1504095881749207713.davem@davemloft.net>
Date: Sat, 23 Jun 2018 10:38:08 +0900 (KST)
From: David Miller <davem@...emloft.net>
To: jeffrey.t.kirsher@...el.com
Cc: me@...in.cc, corbet@....net, linux-doc@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] docs: e100[0] fix build errors
From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
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.
Powered by blists - more mailing lists