[PATCH 1/2] PCI: update pci.txt to talk about pci_alloc_irq_vectors

instead of the deprecated pci_enable_msi* APIs. Signed-off-by: Christoph Hellwig --- Documentation/PCI/pci.txt | 24 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/Documentation/PCI/pci.txt b/Documentation/PCI/pci.txt index

[PATCH 2/2] PCI: update MSI/MSI-X bits in PCIEBUS-HOWTO

Stop talking about low-level details that mention deprecated APIs and concentrate on what service drivers should do and why. Signed-off-by: Christoph Hellwig --- Documentation/PCI/PCIEBUS-HOWTO.txt | 33 +++-- 1 file changed, 7 insertions(+), 26

two small PCI documentation fixups

Avoid mentioning deprecated APIs and make the text a little easier to understand. -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH] crypto: fix typo in doc

On Tue, Feb 14, 2017 at 08:21:45AM +0200, Gilad Ben-Yossef wrote: > Fix a single letter typo in api-skcipher.rst. > > Signed-off-by: Gilad Ben-Yossef Patch applied. Thanks. -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/

Re: [PATCH v2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit

Christopher Covington wrote: The Qualcomm Datacenter Technologies QDF2400 family of SoCs contains a custom (non-PrimeCell) implementation of the SBSA UART. Occasionally the BUSY bit in the Flag Register gets stuck as 1, erratum 44 for both 2432v1 and 2400v1 SoCs. Checking that the Transmit FIFO

Re: [PATCH 00/37] PCI: Support for configurable PCI endpoint

On Wed, Feb 01, 2017 at 06:01:58PM +0530, Kishon Vijay Abraham I wrote: > - list > > Hi Bjorn, > > How do you want to handle this series? I'll send one more version of the > series > including the directory restructuring in the same series. Should it be based > on > your -next? I think if you

Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit

On 02/08/2017 06:04 PM, Timur Tabi wrote: > On 02/08/2017 04:22 PM, Christopher Covington wrote: >> -while (pl011_read(uap, REG_FR) & uap->vendor->fr_busy) >> +while ((pl011_read(uap, REG_FR) ^ uap->vendor->inv_fr) >> +& uap->vendor->fr_busy) >>> >

Re: [PATCH] docs: Make CodingStyle and SubmittingPatches symlinks

(adding Greg KH as I doubt he ever saw the original) On Tue, 2017-02-14 at 14:34 -0700, Jonathan Corbet wrote: > On Mon, 23 Jan 2017 08:34:58 -0200 > Mauro Carvalho Chehab wrote: > > > The main difference between a "pointer file" and a symlink is that the > > first

Re: [PATCH] docs: Make CodingStyle and SubmittingPatches symlinks

On Mon, 23 Jan 2017 08:34:58 -0200 Mauro Carvalho Chehab wrote: > The main difference between a "pointer file" and a symlink is that the > first indicates a temporary solution, teaching people that the > file got renamed and were it is located now. As such, we can

[PATCH linux v8 1/6] hwmon: Add core On-Chip Controller support for POWER CPUs

From: "Edward A. James" Add core support for polling the OCC for it's sensor data and parsing that data into sensor-specific information. Signed-off-by: Edward A. James Signed-off-by: Andrew Jeffery --- Documentation/hwmon/occ| 42

[PATCH linux v8 3/6] hwmon: occ: Add I2C transport implementation for SCOM operations

From: "Edward A. James" Add functions to send SCOM operations over I2C bus. The BMC can communicate with the Power8 host processor over I2C, but needs to use SCOM operations in order to access the OCC register space. Signed-off-by: Edward A. James

[PATCH linux v8 5/6] hwmon: occ: Add hwmon implementation for the P8 OCC

From: "Edward A. James" Add code to tie the hwmon sysfs code and the POWER8 OCC code together, as well as probe the entire driver from the I2C bus. I2C is the communication method between the BMC and the P8 OCC. Signed-off-by: Edward A. James

[PATCH linux v8 6/6] hwmon: occ: Add callbacks for parsing P9 OCC datastructures

From: "Edward A. James" Add functions to parse the data structures that are specific to the OCC on the POWER9 processor. These are the sensor data structures, including temperature, frequency, power, and "caps." Signed-off-by: Edward A. James

[PATCH linux v8 4/6] hwmon: occ: Add callbacks for parsing P8 OCC datastructures

From: "Edward A. James" Add functions to parse the data structures that are specific to the OCC on the POWER8 processor. These are the sensor data structures, including temperature, frequency, power, and "caps." Signed-off-by: Edward A. James

[PATCH linux v8 2/6] hwmon: occ: Add sysfs interface

From: "Edward A. James" Add a generic mechanism to expose the sensors provided by the OCC in sysfs. Signed-off-by: Edward A. James Signed-off-by: Andrew Jeffery --- Documentation/hwmon/occ | 62 +++

[PATCH linux v8 0/6] drivers: hwmon: Add On-Chip Controller driver

From: "Edward A. James" This patchset adds a hwmon driver to support the OCC (On-Chip Controller) on the IBM POWER8 and POWER9 processors, from a BMC (Baseboard Management Controller). The OCC is an embedded processor that provides real time power and thermal monitoring. The

make pdfdocs errors with 4.10-rc8

On a Fedora 25 system, [...] build succeeded, 32 warnings. make PDFLATEX=xelatex LATEXOPTS="-interaction=batchmode" -C Documentation/output/./latex; xelatex -interaction=batchmode 'linux-user.tex' This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016) (preloaded format=xelatex) restricted

Re: [PATCH v4 1/1] DM: inplace compressed DM target (fwd)

ong git tree, please drop us a note to > help improve the system] > > url: > https://github.com/0day-ci/linux/commits/Ram-Pai/DM-inplace-compressed-DM-target/20170214-055727 > base: > https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git > for-next &

Re: [PATCH linux v7 1/6] hwmon: Add core On-Chip Controller support for POWER CPUs

On 02/09/2017 11:31 PM, Joel Stanley wrote: On Wed, Feb 8, 2017 at 9:40 AM, wrote: diff --git a/Documentation/hwmon/occ b/Documentation/hwmon/occ new file mode 100644 index 000..79d1642 --- /dev/null +++ b/Documentation/hwmon/occ The kernel is using

Re: [PATCH] cdrom: Make device operations read-only

On 02/13/2017 05:25 PM, Kees Cook wrote: > Since function tables are a common target for attackers, it's best to keep > them in read-only memory. As such, this makes the CDROM device ops tables > const. This drops additionally n_minors, since it isn't used meaningfully, > and sets the only user of

Re: [PATCH] Add a target to check broken external links in the Documentation

On Tue, 14 Feb 2017 15:22:12 +0100 Remy Leone wrote: > I got another question. There is a lot of broken links. Should I do a big > commit to fix all of them at once? What would be the best workflow to fix > all those errors? I'd suggest starting small, since you're just

Re: [PATCH] Add a target to check broken external links in the Documentation

On Tue, 14 Feb 2017, Jonathan Corbet wrote: > On Tue, 14 Feb 2017 15:52:10 +0200 > Jani Nikula wrote: > >> On Tue, 14 Feb 2017, Remy Leone wrote: >> > I've got a question, when I receive review on a patch, is it better to >> >

Re: [PATCH] Add a target to check broken external links in the Documentation

I got another question. There is a lot of broken links. Should I do a big commit to fix all of them at once? What would be the best workflow to fix all those errors? Best regards Rémy Le 14/02/2017 à 15:15, Jonathan Corbet a écrit : On Tue, 14 Feb 2017 15:52:10 +0200 Jani Nikula

Re: [PATCH] Add a target to check broken external links in the Documentation

On Tue, 14 Feb 2017 15:52:10 +0200 Jani Nikula wrote: > On Tue, 14 Feb 2017, Remy Leone wrote: > > I've got a question, when I receive review on a patch, is it better to > > resubmit or to reply inside the same thread? > > Depends on the

Re: [PATCH] Add a target to check broken external links in the Documentation

On Tue, 14 Feb 2017, Remy Leone wrote: > I've got a question, when I receive review on a patch, is it better to > resubmit or to reply inside the same thread? Depends on the subsystem, maintainer, and the phase of the Moon. ;) I'm not the documentation maintainer, but

Re: [PATCH] Add a target to check broken external links in the Documentation

Hello Thanks for the quick answer. Le 14/02/2017 à 13:28, Jani Nikula a écrit : Hi Remy, I like what this does, and it'll be helpful in ensuring we don't have broken links. However, there are some issues. It's my first Linux kernel patch so this was expected :)

[PATCH v2] Add a target to check broken external links in the Documentation

From: Rémy Léone Documentation shouldn't have broken links. sphinx linkcheck builder scans all documents for external links, tries to open them with urllib2, and writes an overview which ones are broken and redirected to standard output and to output.txt in the output

[PATCH] perf: fix documentation of sysctls perf_event_paranoid and perf_event_mlock_kb

Fix misprint CAP_IOC_LOCK -> CAP_IPC_LOCK. This capability have nothing to do with raw tracepoints. This part is about bypassing mlock limits. Sysctl kernel.perf_event_paranoid = -1 allows raw and ftrace function tracepoints without CAP_SYS_ADMIN. Signed-off-by: Konstantin Khlebnikov

Re: [PATCH] Add a target to check broken external links in the Documentation

Hi Remy, I like what this does, and it'll be helpful in ensuring we don't have broken links. However, there are some issues. On Tue, 14 Feb 2017, Remy Leone wrote: > From: Rémy Léone This area here is for the commit message, describing what linkcheck

[PATCH] Add a target to check broken external links in the Documentation

From: Rémy Léone Signed-off-by: Rémy Léone --- Documentation/Makefile.sphinx | 3 +++ Documentation/conf.py | 2 +- Makefile | 2 +- 3 files changed, 5 insertions(+), 2 deletions(-) diff --git