[PATCH] hwmon: occ: fix err_cast.cocci warnings

drivers/hwmon/occ/occ_sysfs.c:265:9-16: WARNING: ERR_CAST can be used with hwmon -> dev Use ERR_CAST inlined function instead of ERR_PTR(PTR_ERR(...)) Generated by: scripts/coccinelle/api/err_cast.cocci CC: Edward A. James Signed-off-by: Fengguang Wu

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

Hi Edward, [auto build test WARNING on hwmon/hwmon-next] [also build test WARNING on v4.10-rc3 next-20170111] [cannot apply to linux/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits

Re: [PATCH v3 04/10] Documentation: perf: hisi: Documentation for HiP05/06/07 PMU event counting.

On Tuesday 10 January 2017 11:25 PM, Mark Rutland wrote: On Mon, Jan 02, 2017 at 01:49:37AM -0500, Anurup M wrote: +The Hisilicon SoC HiP05/06/07 chips consist of various independent system +device PMU's such as L3 cache(L3C) and Miscellaneous Nodes(MN). +These PMU devices are independent and

Re: [PATCH] Add +~800M crashkernel explaination

On 01/12/2017 at 03:35 AM, Robert LeBlanc wrote: > On Wed, Dec 14, 2016 at 4:17 PM, Xunlei Pang wrote: >> As I replied in another post, if you really want to detail the behaviour, >> should mention >> "crashkernel=size[KMG][@offset[KMG]]" with @offset[KMG] specified >>

Re: [PATCH v4 0/4] Application Data Integrity feature introduced by SPARC M7

On 01/11/2017 04:22 PM, Khalid Aziz wrote: ... > All of the tag coordination can happen in userspace. Once a process sets > a tag on a physical page mapped in its address space, another process > that has mapped the same physical page in its address space can only set > the tag to exact same

Re: [PATCH v4 0/4] Application Data Integrity feature introduced by SPARC M7

On 01/11/2017 12:11 PM, Dave Hansen wrote: On 01/11/2017 10:50 AM, Khalid Aziz wrote: On 01/11/2017 11:13 AM, Dave Hansen wrote: On 01/11/2017 08:56 AM, Khalid Aziz wrote: For memory shared by two different processes, do they have to agree on what the tags are, or can they differ? The two

Re: [RFC 04/10] kmod: provide wrappers for kmod_concurrent inc/dec

On Tue, Jan 10, 2017 at 07:57:10PM +0100, Luis R. Rodriguez wrote: > On Fri, Dec 16, 2016 at 09:05:00AM +0100, Luis R. Rodriguez wrote: > > On Thu, Dec 15, 2016 at 01:46:25PM +0100, Petr Mladek wrote: > > > On Thu 2016-12-08 22:08:59, Luis R. Rodriguez wrote: > > > > On Thu, Dec 08, 2016 at

Re: [PATCH v4 0/4] Application Data Integrity feature introduced by SPARC M7

On 01/11/2017 10:50 AM, Khalid Aziz wrote: > On 01/11/2017 11:13 AM, Dave Hansen wrote: >> On 01/11/2017 08:56 AM, Khalid Aziz wrote: >> For memory shared by two different processes, do they have to agree on >> what the tags are, or can they differ? > > The two processes have to agree on the tag.

Re: [RFC 00/10] kmod: stress test driver, few fixes and enhancements

On Thu, Dec 08, 2016 at 10:47:51AM -0800, Luis R. Rodriguez wrote: > Upon running into an old kmod v19 issue with mount (get_fs_type()) a few of us > hunted for the cause of the issue. Although the issue ended up being a > userspace issue, a stress test driver was written to help reproduce the

Re: [PATCH v4 0/4] Application Data Integrity feature introduced by SPARC M7

On 01/11/2017 11:13 AM, Dave Hansen wrote: On 01/11/2017 08:56 AM, Khalid Aziz wrote: On 01/11/2017 09:33 AM, Dave Hansen wrote: On 01/11/2017 08:12 AM, Khalid Aziz wrote: A userspace task enables ADI through mprotect(). This patch series adds a page protection bit PROT_ADI and a

Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003

[finally, some proper bikeshedding] On 11/01/17 18:40, Timur Tabi wrote: > On 01/11/2017 12:37 PM, Mark Rutland wrote: >> The name, as it is, is perfectly descriptive. >> >> Let's not sacrifice legibility over a non-issue. > > I don't want to kick a dead horse or anything, but changing it to >

Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003

On Wed, Jan 11, 2017 at 12:40:42PM -0600, Timur Tabi wrote: > On 01/11/2017 12:37 PM, Mark Rutland wrote: > >The name, as it is, is perfectly descriptive. > > > >Let's not sacrifice legibility over a non-issue. > > I don't want to kick a dead horse or anything, but changing it to >

Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003

On Wed, Jan 11, 2017 at 06:22:08PM +, Marc Zyngier wrote: > On 11/01/17 18:06, Catalin Marinas wrote: > > On Wed, Jan 11, 2017 at 09:41:15AM -0500, Christopher Covington wrote: > >> diff --git a/arch/arm64/mm/proc.S b/arch/arm64/mm/proc.S > >> index 32682be..9ee46df 100644 > >> ---

Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003

On 01/11/2017 12:37 PM, Mark Rutland wrote: The name, as it is, is perfectly descriptive. Let's not sacrifice legibility over a non-issue. I don't want to kick a dead horse or anything, but changing it to QCOM_FLKR_ERRATUM_1003 would eliminate all the spacing problems without sacrificing

Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003

On Wed, Jan 11, 2017 at 12:35:55PM -0600, Timur Tabi wrote: > On 01/11/2017 12:33 PM, Mark Rutland wrote: > >It'll need to affect all lines since the kconfig column needs to expand > >by at least one character to fit QCOM_FALKOR_ERRATUM_1003. > > Or we can make the macro shorter. The name, as it

Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003

On 01/11/2017 12:33 PM, Mark Rutland wrote: It'll need to affect all lines since the kconfig column needs to expand by at least one character to fit QCOM_FALKOR_ERRATUM_1003. Or we can make the macro shorter. -- Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies,

Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003

On Wed, Jan 11, 2017 at 06:06:27PM +, Catalin Marinas wrote: > On Wed, Jan 11, 2017 at 09:41:15AM -0500, Christopher Covington wrote: > > -| Implementor| Component | Erratum ID | Kconfig > > | > > +| Implementor | Component | Erratum ID | Kconfig

Re: [RFC 09/10] kmod: add helpers for getting kmod count and limit

On Fri, Dec 16, 2016 at 08:57:26AM +0100, Luis R. Rodriguez wrote: > On Thu, Dec 15, 2016 at 05:56:19PM +0100, Petr Mladek wrote: > > On Thu 2016-12-08 11:49:20, Luis R. Rodriguez wrote: > > > This adds helpers for getting access to the kmod count and limit from > > > userspace. While at it, this

Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003

On 11/01/17 18:06, Catalin Marinas wrote: > Some minor comments below, nothing fundamental (as long as you say the > new sequence doesn't have the speculative TLB load problem I mentioned > on a previous version). > > On Wed, Jan 11, 2017 at 09:41:15AM -0500, Christopher Covington wrote: >> diff

Re: [Linux-c6x-dev] [PATCH v2 7/7] uapi: export all headers under uapi directories

On Fri, 2017-01-06 at 10:43 +0100, Nicolas Dichtel wrote: > Regularly, when a new header is created in include/uapi/, the developer > forgets to add it in the corresponding Kbuild file. This error is usually > detected after the release is out. > > In fact, all headers under uapi directories

[PATCH linux v2 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| 40

Re: [PATCH v4 0/4] Application Data Integrity feature introduced by SPARC M7

On 01/11/2017 08:56 AM, Khalid Aziz wrote: > On 01/11/2017 09:33 AM, Dave Hansen wrote: >> On 01/11/2017 08:12 AM, Khalid Aziz wrote: >>> A userspace task enables ADI through mprotect(). This patch series adds >>> a page protection bit PROT_ADI and a corresponding VMA flag >>> VM_SPARC_ADI.

[PATCH linux v2 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 v2 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

[PATCH linux v2 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 v2 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 v2 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 v2 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

Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003

Some minor comments below, nothing fundamental (as long as you say the new sequence doesn't have the speculative TLB load problem I mentioned on a previous version). On Wed, Jan 11, 2017 at 09:41:15AM -0500, Christopher Covington wrote: > diff --git a/Documentation/arm64/silicon-errata.txt >

Re: [PATCH v4 0/4] Application Data Integrity feature introduced by SPARC M7

On 01/11/2017 08:12 AM, Khalid Aziz wrote: > A userspace task enables ADI through mprotect(). This patch series adds > a page protection bit PROT_ADI and a corresponding VMA flag > VM_SPARC_ADI. VM_SPARC_ADI is used to trigger setting TTE.mcd bit in the > sparc pte that enables ADI checking on the

[PATCH v4 4/4] sparc64: Add support for ADI (Application Data Integrity)

ADI is a new feature supported on SPARC M7 and newer processors to allow hardware to catch rogue accesses to memory. ADI is supported for data fetches only and not instruction fetches. An app can enable ADI on its data pages, set version tags on them and use versioned addresses to access the data

[PATCH v4 0/4] Application Data Integrity feature introduced by SPARC M7

SPARC M7 processor adds additional metadata for memory address space that can be used to secure access to regions of memory. This additional metadata is implemented as a 4-bit tag attached to each cacheline size block of memory. A task can set a tag on any number of such blocks. Access to such

Re: [PATCH 3/5] pinctrl: sunxi: add driver for V3s SoC

On Tue, Jan 3, 2017 at 4:16 PM, Icenowy Zheng wrote: > V3s SoC features only a pin controller (for the lack of CPUs part). > > Add a driver for this controller. > > Signed-off-by: Icenowy Zheng Patch applied with Maxime's ACK. Yours, Linus Walleij -- To

[PATCH v3 5/5] arm64: Work around Falkor erratum 1009

During a TLB invalidate sequence targeting the inner shareable domain, Falkor may prematurely complete the DSB before all loads and stores using the old translation are observed; instruction fetches are not subject to the conditions of this erratum. Signed-off-by: Christopher Covington

[PATCH v3 2/5] arm64: Work around Falkor erratum 1003

From: Shanker Donthineni On the Qualcomm Datacenter Technologies Falkor v1 CPU, memory accesses may allocate TLB entries using an incorrect ASID when TTBRx_EL1 is being updated. Changing the TTBRx_EL1[ASID] and TTBRx_EL1[BADDR] fields separately using a reserved ASID

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

On Wed, 11 Jan 2017, Joe Perches wrote: > On Wed, 2017-01-11 at 10:54 +0200, Jani Nikula wrote: >> On Wed, 11 Jan 2017, Joe Perches wrote: >> > Make these files symlinks to the .rst equivalents >> >> If we're going to do this (and I really don't mind either

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

On Wed, 2017-01-11 at 10:54 +0200, Jani Nikula wrote: > On Wed, 11 Jan 2017, Joe Perches wrote: > > Make these files symlinks to the .rst equivalents > > If we're going to do this (and I really don't mind either way), then > please add > > Fixes: 08a9a8d44c1c ("doc: re-add

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

On Wed, 11 Jan 2017, Joe Perches wrote: > Make these files symlinks to the .rst equivalents If we're going to do this (and I really don't mind either way), then please add Fixes: 08a9a8d44c1c ("doc: re-add CodingStyle and SubmittingPatches") and queue to v4.10-rc. BR, Jani.

Re: [PATCH] doc: add note on usleep_range range

On Tue, Jan 10, 2017 at 10:25:29PM +0100, Pavel Machek wrote: > Hi! > > > > "to have zero jitter" at least. I believe it is "does not". > > > > > > I don't see how atomic vs. non-atomic context makes difference. There > > > are sources of jitter that affect atomic context... > > > > The

Re: [PATCH v4 2/3] watchdog: introduce watchdog.open_timeout commandline parameter

On 2017-01-10 19:08, Guenter Roeck wrote: On Mon, Jan 09, 2017 at 04:02:32PM +0100, Rasmus Villemoes wrote: +static unsigned open_timeout; +module_param(open_timeout, uint, 0644); + +static bool watchdog_past_open_deadline(struct watchdog_core_data *data) +{ + if (!open_timeout) +