[PULL] Documentation changes for 4.10

2016-12-11 Thread Jonathan Corbet
The following changes since commit bc33b0ca11e3df46a4fa7639ba488c9d4911: Linux 4.9-rc4 (2016-11-05 16:23:36 -0700) are available in the git repository at: git://git.lwn.net/linux.git tags/docs-4.10 for you to fetch changes up to 868c97a846a73e937d835b09b8c885a69df50ec8: dma-buf: Extr

[PATCH] tty: serial: lantiq: implement earlycon support

2016-12-11 Thread Martin Blumenstingl
This allows enabling earlycon for devices with a Lantiq serial console by splitting lqasc_serial_port_write() from lqasc_console_write() and re-using the new function for earlycon's write callback. The kernel-parameter name matches the driver name ("lantiq"), similar to how other drivers implement

Re: [PATCH 1/5] dma-buf: Extract dma-buf.rst

2016-12-11 Thread Jonathan Corbet
On Fri, 9 Dec 2016 19:53:05 +0100 Daniel Vetter wrote: > Just prep work to polish and consolidate all the dma-buf related > documenation. > > Unfortunately I didn't discover a way to both integrate this new file > into the overall toc while keeping it at the current place. Work > around that by

Re: [PATCH 0/5] sphinxification for dma-buf docs

2016-12-11 Thread Jonathan Corbet
On Sun, 11 Dec 2016 18:35:42 +0100 Daniel Vetter wrote: > > Here's a thought, though: how about if we slip in a little version of > > dma-buf.rst now with a "coming soon, don't miss it!!" message? Then the > > rest of the set could go through your tree without touching > > driver-api/index.rst a

Re: [PATCH 0/5] sphinxification for dma-buf docs

2016-12-11 Thread Daniel Vetter
On Sun, Dec 11, 2016 at 4:11 PM, Jonathan Corbet wrote: > On Sun, 11 Dec 2016 13:35:49 +0100 > Daniel Vetter wrote: > >> > It seems like just the sort of thing we want to be doing to pull the docs >> > together in a more rational way. >> >> Ok if we pull this in through gfx trees? Will miss 4.10

Re: [PATCH 0/5] sphinxification for dma-buf docs

2016-12-11 Thread Jonathan Corbet
On Sun, 11 Dec 2016 13:35:49 +0100 Daniel Vetter wrote: > > It seems like just the sort of thing we want to be doing to pull the docs > > together in a more rational way. > > Ok if we pull this in through gfx trees? Will miss 4.10 though, that's > already finished and in bugfix-only mode. I'v

Re: [PATCH 0/5] sphinxification for dma-buf docs

2016-12-11 Thread Daniel Vetter
On Fri, Dec 9, 2016 at 10:15 PM, Jonathan Corbet wrote: > On Fri, 9 Dec 2016 19:53:04 +0100 > Daniel Vetter wrote: > >> Not yet everything in this area, I still want to sprinkle nice docs around >> all >> the fence code. Especially some text to explain implicit vs. explicit fencing >> and how i

Re: [PATCH 0/5] sphinxification for dma-buf docs

2016-12-11 Thread Sumit Semwal
Hi Daniel, On 10 December 2016 at 02:45, Jonathan Corbet wrote: > On Fri, 9 Dec 2016 19:53:04 +0100 > Daniel Vetter wrote: > >> Not yet everything in this area, I still want to sprinkle nice docs around >> all >> the fence code. Especially some text to explain implicit vs. explicit fencing >>

Re: ILP32 for ARM64 - testing with lmbench

2016-12-11 Thread Yury Norov
On Mon, Dec 05, 2016 at 02:13:12PM +, Catalin Marinas wrote: > On Mon, Dec 05, 2016 at 06:16:09PM +0800, Zhangjian (Bamvor) wrote: > > Do you have suggestion of next move of upstreaming ILP32? > > I mentioned the steps a few time before. I'm pasting them again here: > > 1. Complete the review

[linux-next:master 7186/11555] htmldocs: Documentation/doc-guide/sphinx.rst:110: ERROR: Unknown target name: "sphinx c domain".

2016-12-11 Thread kbuild test robot
Hi Mauro, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master head: 4a71e4389b1f8bbf02f43522c234143fd571dcb8 commit: 1dc4bbf0b268246f6202c761016735933b6f0b99 [7186/11555] docs-rst: doc-guide: split the kernel-documentation.r