Re: STRICT_KERNEL_RWX on PPC32 is broken on PowerMac G4

> > > How early does it hang ? Any oops or trace ? > > > > Very early - instead oif kernel emssages, I see some repeated gibberish > > of some characteers, and the background turns white. > > I am booting from yaboot, background is normally black. > > Ok, could you try by replacing #ifdef

Re: STRICT_KERNEL_RWX on PPC32 is broken on PowerMac G4

> > > How early does it hang ? Any oops or trace ? > > > > Very early - instead oif kernel emssages, I see some repeated gibberish > > of some characteers, and the background turns white. > > I am booting from yaboot, background is normally black. > > Ok, could you try by replacing #ifdef

Re: Linux 3.10.108 (EOL)

Am 18.11.2017 um 00:46 schrieb Alan Cox: i just wanted to throw some stones on the bloated kernel problem which is increasing People used to be working on that, but then it seemed like the "size" got to a point that people were comfortable with it. Are you sure that There's also a lot of

Re: Linux 3.10.108 (EOL)

Am 18.11.2017 um 00:46 schrieb Alan Cox: i just wanted to throw some stones on the bloated kernel problem which is increasing People used to be working on that, but then it seemed like the "size" got to a point that people were comfortable with it. Are you sure that There's also a lot of

Re: Linux 3.10.108 (EOL)

On Fri, Nov 17, 2017 at 11:46:20PM +, Alan Cox wrote: > > > i just wanted to throw some stones on the bloated kernel problem which is > > > increasing > > > > People used to be working on that, but then it seemed like the "size" > > got to a point that people were comfortable with it. Are

Re: Linux 3.10.108 (EOL)

On Fri, Nov 17, 2017 at 11:46:20PM +, Alan Cox wrote: > > > i just wanted to throw some stones on the bloated kernel problem which is > > > increasing > > > > People used to be working on that, but then it seemed like the "size" > > got to a point that people were comfortable with it. Are

Re: [PATCH] rdma: Add Jason as a co-maintainer

On Fri, Nov 17, 2017 at 08:44:27PM -0500, Doug Ledford wrote: > > If you split step 5 above into 5a) Push from local work repo to local > prep repo and 5b) Do full kernel build in prep repo to test that all > code needed to compile is tracked by git, it would catch that mistake > before it makes

Re: [PATCH] rdma: Add Jason as a co-maintainer

On Fri, Nov 17, 2017 at 08:44:27PM -0500, Doug Ledford wrote: > > If you split step 5 above into 5a) Push from local work repo to local > prep repo and 5b) Do full kernel build in prep repo to test that all > code needed to compile is tracked by git, it would catch that mistake > before it makes

Re: [PATCH 2/4] btrfs: make open_ctree error injectable

* Josef Bacik wrote: > From: Josef Bacik > > This allows us to do error injection with BPF for open_ctree. > > Signed-off-by: Josef Bacik > --- > fs/btrfs/disk-io.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git

Re: [PATCH 2/4] btrfs: make open_ctree error injectable

* Josef Bacik wrote: > From: Josef Bacik > > This allows us to do error injection with BPF for open_ctree. > > Signed-off-by: Josef Bacik > --- > fs/btrfs/disk-io.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c > index

[PATCH] perf report/top: Add a tip about source line matching

Cc: Jiri Olsa Cc: Namhyung Kim Cc: Taeung Song --- tools/perf/Documentation/tips.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/Documentation/tips.txt b/tools/perf/Documentation/tips.txt index db0ca30..b60616a

[PATCH] perf report/top: Add a tip about source line matching

Cc: Jiri Olsa Cc: Namhyung Kim Cc: Taeung Song --- tools/perf/Documentation/tips.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/Documentation/tips.txt b/tools/perf/Documentation/tips.txt index db0ca30..b60616a 100644 --- a/tools/perf/Documentation/tips.txt +++

Re: [RFC PATCH 00/20] Intel(R) Resource Director Technology Cache Pseudo-Locking enabling

Hi Thomas, On 11/17/2017 4:48 PM, Thomas Gleixner wrote: > On Mon, 13 Nov 2017, Reinette Chatre wrote: > > thanks for that interesting work. Before I start looking into the details > in the next days let me ask a few general questions first. Thank you very much for taking a look. I look forward

Re: [RFC PATCH 00/20] Intel(R) Resource Director Technology Cache Pseudo-Locking enabling

Hi Thomas, On 11/17/2017 4:48 PM, Thomas Gleixner wrote: > On Mon, 13 Nov 2017, Reinette Chatre wrote: > > thanks for that interesting work. Before I start looking into the details > in the next days let me ask a few general questions first. Thank you very much for taking a look. I look forward

[PATCH 0/3] mfd: Handle platform_get_irq's error checking and return

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct and we must check its return value. Arvind Yadav (3): [PATCH 1/3] mfd: ipaq-micro: Fix platform_get_irq's error checking [PATCH

[PATCH 0/3] mfd: Handle platform_get_irq's error checking and return

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct and we must check its return value. Arvind Yadav (3): [PATCH 1/3] mfd: ipaq-micro: Fix platform_get_irq's error checking [PATCH

[PATCH 2/3] mfd: intel-lpss: Handle return value of platform_get_*

platform_get_irq() and platform_get_resource() can fail here and we must check its return value. Signed-off-by: Arvind Yadav --- drivers/mfd/intel-lpss-acpi.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/mfd/intel-lpss-acpi.c

[PATCH 3/3] mfd: sun4i-gpadc: Handle return value of platform_get_irq

platform_get_irq() can fail here and we must check its return value. Signed-off-by: Arvind Yadav --- drivers/mfd/sun4i-gpadc.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/mfd/sun4i-gpadc.c b/drivers/mfd/sun4i-gpadc.c index

[PATCH 1/3] mfd: ipaq-micro: Fix platform_get_irq's error checking

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Signed-off-by: Arvind Yadav --- drivers/mfd/ipaq-micro.c | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH 2/3] mfd: intel-lpss: Handle return value of platform_get_*

platform_get_irq() and platform_get_resource() can fail here and we must check its return value. Signed-off-by: Arvind Yadav --- drivers/mfd/intel-lpss-acpi.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/mfd/intel-lpss-acpi.c b/drivers/mfd/intel-lpss-acpi.c index

[PATCH 3/3] mfd: sun4i-gpadc: Handle return value of platform_get_irq

platform_get_irq() can fail here and we must check its return value. Signed-off-by: Arvind Yadav --- drivers/mfd/sun4i-gpadc.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/mfd/sun4i-gpadc.c b/drivers/mfd/sun4i-gpadc.c index 9cfc881..1c89235 100644 ---

[PATCH 1/3] mfd: ipaq-micro: Fix platform_get_irq's error checking

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Signed-off-by: Arvind Yadav --- drivers/mfd/ipaq-micro.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 1/2] misc: aspeed-lpc-snoop: Fix platform_get_irq's error checking

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Signed-off-by: Arvind Yadav --- drivers/misc/aspeed-lpc-snoop.c | 4 ++-- 1 file changed, 2

[PATCH 2/2] misc: atmel-ssc: Fix platform_get_irq's error checking

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Signed-off-by: Arvind Yadav --- drivers/misc/atmel-ssc.c | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH 1/2] misc: aspeed-lpc-snoop: Fix platform_get_irq's error checking

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Signed-off-by: Arvind Yadav --- drivers/misc/aspeed-lpc-snoop.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[PATCH 2/2] misc: atmel-ssc: Fix platform_get_irq's error checking

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Signed-off-by: Arvind Yadav --- drivers/misc/atmel-ssc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 0/2] misc: Fix platform_get_irq's error checking

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Arvind Yadav (2): [PATCH 1/2] misc: aspeed-lpc-snoop: Fix platform_get_irq's error checking [PATCH 2/2] misc: atmel-ssc: Fix

[PATCH 0/2] misc: Fix platform_get_irq's error checking

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Arvind Yadav (2): [PATCH 1/2] misc: aspeed-lpc-snoop: Fix platform_get_irq's error checking [PATCH 2/2] misc: atmel-ssc: Fix

Re: [nfsd4] potentially hardware breaking regression in 4.14-rc and 4.13.11

On Fri, Nov 17, 2017 at 9:14 PM, Kees Cook wrote: > > FWIW, myself doing a build at d9e12200852d with and without > GCC_PLUGIN_RANDSTRUCT _appears_ to produce identical objdump output > where I did spot-checks. That would probably be a good thing to check anyway - check

Re: [nfsd4] potentially hardware breaking regression in 4.14-rc and 4.13.11

On Fri, Nov 17, 2017 at 9:14 PM, Kees Cook wrote: > > FWIW, myself doing a build at d9e12200852d with and without > GCC_PLUGIN_RANDSTRUCT _appears_ to produce identical objdump output > where I did spot-checks. That would probably be a good thing to check anyway - check the difference between

[PATCH 2/5 v2] ASoC: mt8173: Fix platform_get_irq's error checking

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Signed-off-by: Arvind Yadav --- chnages in v2 : irq_id was unsigned. so changed it to

[PATCH 2/5 v2] ASoC: mt8173: Fix platform_get_irq's error checking

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Signed-off-by: Arvind Yadav --- chnages in v2 : irq_id was unsigned. so changed it to signed.

[PATCH 1/5 v2] ASoC: ep93xx-ac97: Fix platform_get_irq's error checking

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Signed-off-by: Arvind Yadav --- changes in v2 : irq was unsigned. so changed it to signed.

[PATCH 3/5 v2] ASoC: nuc900: Fix platform_get_irq's error checking

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Signed-off-by: Arvind Yadav --- changes in v2 : nuc900_audio->irq_num is unsigned. so handle

[PATCH 1/5 v2] ASoC: ep93xx-ac97: Fix platform_get_irq's error checking

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Signed-off-by: Arvind Yadav --- changes in v2 : irq was unsigned. so changed it to signed.

[PATCH 3/5 v2] ASoC: nuc900: Fix platform_get_irq's error checking

The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Signed-off-by: Arvind Yadav --- changes in v2 : nuc900_audio->irq_num is unsigned. so handle through signed variable.

Re: Blank console but X11 works on MCP79 - old regression since 3.8

On Fri, Nov 17, 2017 at 2:37 PM, Ilia Mirkin wrote: > On Fri, Nov 17, 2017 at 2:25 PM, Ondrej Zary > wrote: >> On Friday 17 November 2017 18:41:17 Ilia Mirkin wrote: >>> On Fri, Nov 17, 2017 at 12:33 PM, Ondrej Zary >>> >>>

Re: Blank console but X11 works on MCP79 - old regression since 3.8

On Fri, Nov 17, 2017 at 2:37 PM, Ilia Mirkin wrote: > On Fri, Nov 17, 2017 at 2:25 PM, Ondrej Zary > wrote: >> On Friday 17 November 2017 18:41:17 Ilia Mirkin wrote: >>> On Fri, Nov 17, 2017 at 12:33 PM, Ondrej Zary >>> >>> wrote: >>> > @@ -483,8 +483,8 @@ >>> > nouveau :02:00.0: disp:

RE: [virtio-dev] Re: [PATCH v17 6/6] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_VQ

On Friday, November 17, 2017 8:45 PM, Michael S. Tsirkin wrote: > On Fri, Nov 17, 2017 at 07:35:03PM +0800, Wei Wang wrote: > > On 11/16/2017 09:27 PM, Wei Wang wrote: > > > On 11/16/2017 04:32 AM, Michael S. Tsirkin wrote: > > > > On Fri, Nov 03, 2017 at 04:13:06PM +0800, Wei Wang wrote: > > > >

RE: [virtio-dev] Re: [PATCH v17 6/6] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_VQ

On Friday, November 17, 2017 8:45 PM, Michael S. Tsirkin wrote: > On Fri, Nov 17, 2017 at 07:35:03PM +0800, Wei Wang wrote: > > On 11/16/2017 09:27 PM, Wei Wang wrote: > > > On 11/16/2017 04:32 AM, Michael S. Tsirkin wrote: > > > > On Fri, Nov 03, 2017 at 04:13:06PM +0800, Wei Wang wrote: > > > >

Re: [PATCH] checkpatch: allow URL >80 chars

On Fri, 2017-11-17 at 16:56 +0100, Andreas Brauchli wrote: > Allow URL to exceed the 80 char limit for improved interaction in > adaption to ongoing but undocumented practice. > > $ git grep -E '://\S{77}.*' -- '*.[ch]' > > The patch checks that the URL is indeed on its own line in that it >

Re: [PATCH] checkpatch: allow URL >80 chars

On Fri, 2017-11-17 at 16:56 +0100, Andreas Brauchli wrote: > Allow URL to exceed the 80 char limit for improved interaction in > adaption to ongoing but undocumented practice. > > $ git grep -E '://\S{77}.*' -- '*.[ch]' > > The patch checks that the URL is indeed on its own line in that it >

Re: [nfsd4] potentially hardware breaking regression in 4.14-rc and 4.13.11

On Fri, Nov 17, 2017 at 5:54 PM, Patrick McLean wrote: > On 2017-11-17 04:55 PM, Linus Torvalds wrote: >> On Fri, Nov 17, 2017 at 4:27 PM, Patrick McLean wrote: >>> >>> I am still getting the crash at d9e12200852d, I figured I would >>> double-check the

Re: [nfsd4] potentially hardware breaking regression in 4.14-rc and 4.13.11

On Fri, Nov 17, 2017 at 5:54 PM, Patrick McLean wrote: > On 2017-11-17 04:55 PM, Linus Torvalds wrote: >> On Fri, Nov 17, 2017 at 4:27 PM, Patrick McLean wrote: >>> >>> I am still getting the crash at d9e12200852d, I figured I would >>> double-check the "good" and "bad" kernels before starting a

[PATCH] certs: always use secondary keyring first if possible

Commit d3bfe84129f6 introduced secondary_trusted_keys keyring, current users of verify_pkcs7_signature are below: net/wireless/reg.c : uses its own trusted_keys kernel/module_signing.c : pass NULL trusted_keys crypto/asymmetric_keys/verify_pefile.c : pass NULL trusted_keys For both module and

[PATCH] certs: always use secondary keyring first if possible

Commit d3bfe84129f6 introduced secondary_trusted_keys keyring, current users of verify_pkcs7_signature are below: net/wireless/reg.c : uses its own trusted_keys kernel/module_signing.c : pass NULL trusted_keys crypto/asymmetric_keys/verify_pefile.c : pass NULL trusted_keys For both module and

Re: [PATCH v2 12/15] ima: do not update security.ima if appraisal status is not INTEGRITY_PASS

On Tue, Nov 07, 2017 at 11:37:07AM +0100, Roberto Sassu wrote: > Commit b65a9cfc2c38 ("Untangling ima mess, part 2: deal with counters") > moved the call of ima_file_check() from may_open() to do_filp_open() at a > point where the file descriptor is already opened. > > This breaks the assumption

Re: [PATCH v2 12/15] ima: do not update security.ima if appraisal status is not INTEGRITY_PASS

On Tue, Nov 07, 2017 at 11:37:07AM +0100, Roberto Sassu wrote: > Commit b65a9cfc2c38 ("Untangling ima mess, part 2: deal with counters") > moved the call of ima_file_check() from may_open() to do_filp_open() at a > point where the file descriptor is already opened. > > This breaks the assumption

Re: [PATCH 1/2] vfio/type1: Adopt fast IOTLB flush interface when unmap IOVAs

On Fri, 17 Nov 2017 14:51:52 -0700 Alex Williamson wrote: > On Fri, 17 Nov 2017 15:11:19 -0600 > Suravee Suthikulpanit wrote: > > > From: Suravee Suthikulpanit > > > > VFIO IOMMU type1 currently upmaps

Re: [PATCH 1/2] vfio/type1: Adopt fast IOTLB flush interface when unmap IOVAs

On Fri, 17 Nov 2017 14:51:52 -0700 Alex Williamson wrote: > On Fri, 17 Nov 2017 15:11:19 -0600 > Suravee Suthikulpanit wrote: > > > From: Suravee Suthikulpanit > > > > VFIO IOMMU type1 currently upmaps IOVA pages synchronously, which requires > > IOTLB flushing for every unmapping. This

Re: [PATCH v2 06/15] ima: add parser of digest lists metadata

On Tue, Nov 07, 2017 at 11:37:01AM +0100, Roberto Sassu wrote: > from a predefined position (/etc/ima/digest_lists/metadata), when rootfs > becomes available. Digest lists must be loaded before IMA appraisal is in > enforcing mode. I'm sure there's a good reason for it, but this seems weird to

Re: [PATCH v2 06/15] ima: add parser of digest lists metadata

On Tue, Nov 07, 2017 at 11:37:01AM +0100, Roberto Sassu wrote: > from a predefined position (/etc/ima/digest_lists/metadata), when rootfs > becomes available. Digest lists must be loaded before IMA appraisal is in > enforcing mode. I'm sure there's a good reason for it, but this seems weird to

Re: Disk UUID failing query in 4.14-rc5

On 10/24/2017 08:14 AM, tedheadster wrote: > There has been some change between the 4.13 and 4.14-rc5 kernel. I am > using the same userspace with those two kernels. 4.13 successfully > reports the UUID using 'blkid /dev/sdX' for all cases. > > However, when I switch to the 4.14-rc5 kernel, I can

Re: Disk UUID failing query in 4.14-rc5

On 10/24/2017 08:14 AM, tedheadster wrote: > There has been some change between the 4.13 and 4.14-rc5 kernel. I am > using the same userspace with those two kernels. 4.13 successfully > reports the UUID using 'blkid /dev/sdX' for all cases. > > However, when I switch to the 4.14-rc5 kernel, I can

Re: [PATCH v3] kbuild: Set KBUILD_CFLAGS before incl. arch Makefile

2017-11-16 5:42 GMT+09:00 Nick Desaulniers : > From: Chris Fries > > Set the clang KBUILD_CFLAGS up before including arch/ Makefiles, > so that ld-options (etc.) can work correctly. > > This fixes errors with clang such as ld-options trying to CC >

Re: [PATCH v3] kbuild: Set KBUILD_CFLAGS before incl. arch Makefile

2017-11-16 5:42 GMT+09:00 Nick Desaulniers : > From: Chris Fries > > Set the clang KBUILD_CFLAGS up before including arch/ Makefiles, > so that ld-options (etc.) can work correctly. > > This fixes errors with clang such as ld-options trying to CC > against your host architecture, but LD trying to

Re: [PATCH 2/2] kbuild: remove all dummy assignments to obj-

2017-11-08 1:31 GMT+09:00 Masahiro Yamada : > Now kbuild core scripts create empty built-in.o where necessary. > Remove "obj- := dummy.o" tricks. > > Signed-off-by: Masahiro Yamada > --- > Applied to linux-kbuild/kbuild. -- Best

Re: [PATCH 2/2] kbuild: remove all dummy assignments to obj-

2017-11-08 1:31 GMT+09:00 Masahiro Yamada : > Now kbuild core scripts create empty built-in.o where necessary. > Remove "obj- := dummy.o" tricks. > > Signed-off-by: Masahiro Yamada > --- > Applied to linux-kbuild/kbuild. -- Best Regards Masahiro Yamada

Re: [PATCH 1/2] kbuild: create built-in.o automatically if parent directory wants it

2017-11-08 1:31 GMT+09:00 Masahiro Yamada : > "obj-y += foo/" syntax requires Kbuild to visit the "foo" subdirectory > and link built-in.o from that directory. This means foo/Makefile is > responsible for creating built-in.o even if there is no object to > link (in

Re: [PATCH 1/2] kbuild: create built-in.o automatically if parent directory wants it

2017-11-08 1:31 GMT+09:00 Masahiro Yamada : > "obj-y += foo/" syntax requires Kbuild to visit the "foo" subdirectory > and link built-in.o from that directory. This means foo/Makefile is > responsible for creating built-in.o even if there is no object to > link (in this case, built-in.o is an

[PATCH v5 3/4] pmbus (core): Add virtual page config bit

Some circumstances call for virtual pages, to expose multiple values packed into an extended PMBus register in a manner non-compliant with the PMBus standard. An example of this is the Maxim MAX31785 controller, which extends the READ_FAN_SPEED_1 PMBus register from two to four bytes to support

[PATCH v5 3/4] pmbus (core): Add virtual page config bit

Some circumstances call for virtual pages, to expose multiple values packed into an extended PMBus register in a manner non-compliant with the PMBus standard. An example of this is the Maxim MAX31785 controller, which extends the READ_FAN_SPEED_1 PMBus register from two to four bytes to support

[PATCH v5 4/4] pmbus (max31785): Add dual tachometer support

The dual tachometer feature is implemented in hardware with a TACHSEL input to indicate the rotor under measurement, and exposed on the device by extending the READ_FAN_SPEED_1 word with two extra bytes*. The need to read the non-standard four-byte response leads to a cut-down implementation of

[PATCH v5 0/4] pmbus: Expand fan support and add MAX31785 driver

Hello, This series introduces support for the MAX31785 intelligent fan controller, a PMBus device providing closed-loop fan control among a number of other features. Along the way the series adds support to control fans and create virtual pages to the PMBus core, the latter to support some of the

[PATCH v5 1/4] pmbus (core): Add fan control support

Expose fanX_target, pwmX and pwmX_enable hwmon sysfs attributes. Fans in a PMBus device are driven by the configuration of two registers, FAN_CONFIG_x_y and FAN_COMMAND_x: FAN_CONFIG_x_y dictates how the fan and the tacho operate (if installed), while FAN_COMMAND_x sets the desired fan rate. The

[PATCH v5 2/4] pmbus (max31785): Add fan control

The implementation makes use of the new fan control virtual registers exposed by the pmbus core. It mixes use of the default implementations with some overrides via the read/write handlers to handle FAN_COMMAND_1 on the MAX31785, whose definition breaks the value range into various control bands

[PATCH v5 4/4] pmbus (max31785): Add dual tachometer support

The dual tachometer feature is implemented in hardware with a TACHSEL input to indicate the rotor under measurement, and exposed on the device by extending the READ_FAN_SPEED_1 word with two extra bytes*. The need to read the non-standard four-byte response leads to a cut-down implementation of

[PATCH v5 0/4] pmbus: Expand fan support and add MAX31785 driver

Hello, This series introduces support for the MAX31785 intelligent fan controller, a PMBus device providing closed-loop fan control among a number of other features. Along the way the series adds support to control fans and create virtual pages to the PMBus core, the latter to support some of the

[PATCH v5 1/4] pmbus (core): Add fan control support

Expose fanX_target, pwmX and pwmX_enable hwmon sysfs attributes. Fans in a PMBus device are driven by the configuration of two registers, FAN_CONFIG_x_y and FAN_COMMAND_x: FAN_CONFIG_x_y dictates how the fan and the tacho operate (if installed), while FAN_COMMAND_x sets the desired fan rate. The

[PATCH v5 2/4] pmbus (max31785): Add fan control

The implementation makes use of the new fan control virtual registers exposed by the pmbus core. It mixes use of the default implementations with some overrides via the read/write handlers to handle FAN_COMMAND_1 on the MAX31785, whose definition breaks the value range into various control bands

[GIT PULL] hwmon updates for v4.15 (take 2)

Hi Linus, Please pull hwmon updates for Linux v4.15 from signed tag: git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-for-linus-v4.15-take2 Thanks, Guenter -- The following changes since commit e60e1ee60630cafef5e430c2ae364877e061d980: Merge tag

[GIT PULL] hwmon updates for v4.15 (take 2)

Hi Linus, Please pull hwmon updates for Linux v4.15 from signed tag: git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-for-linus-v4.15-take2 Thanks, Guenter -- The following changes since commit e60e1ee60630cafef5e430c2ae364877e061d980: Merge tag

Re: [v2,12/18] kbuild: add support for clang LTO

On Wed, 15 Nov 2017 13:34:22 -0800 Sami Tolvanen wrote: > This change adds the configuration option CONFIG_LTO_CLANG, and > build system support for clang's Link Time Optimization (LTO). In > preparation for LTO support for other compilers, potentially common > parts of

Re: [v2,12/18] kbuild: add support for clang LTO

On Wed, 15 Nov 2017 13:34:22 -0800 Sami Tolvanen wrote: > This change adds the configuration option CONFIG_LTO_CLANG, and > build system support for clang's Link Time Optimization (LTO). In > preparation for LTO support for other compilers, potentially common > parts of the changes are gated

Re: [PATCH AUTOSEL for 4.9 36/56] drm/i915: Fix the level 0 max_wm hack on VLV/CHV

On Fri, Nov 17, 2017 at 03:01:08PM +0200, Jani Nikula wrote: >I still have no idea how this autoselect picks up patches that do *not* >have cc: stable nor Fixes: from us. What information do you have that we >don't for making that call? I think there's a difference in views about the stable tag

Re: [PATCH AUTOSEL for 4.9 36/56] drm/i915: Fix the level 0 max_wm hack on VLV/CHV

On Fri, Nov 17, 2017 at 03:01:08PM +0200, Jani Nikula wrote: >I still have no idea how this autoselect picks up patches that do *not* >have cc: stable nor Fixes: from us. What information do you have that we >don't for making that call? I think there's a difference in views about the stable tag

[GIT] Sparc

1) Add missing cmpxchg64() for 32-bit sparc. 2) Timer conversions from Allen Pais and Kees Cook. 3) vDSO support, from Nagarathnam Muthusamy. 4) Fix sparc64 huge page table walks based upon bug report by Al Viro, from Nitin Gupta. 5) Optimized fls() for T4 and above, from Vijay Kumar.

[GIT] Sparc

1) Add missing cmpxchg64() for 32-bit sparc. 2) Timer conversions from Allen Pais and Kees Cook. 3) vDSO support, from Nagarathnam Muthusamy. 4) Fix sparc64 huge page table walks based upon bug report by Al Viro, from Nitin Gupta. 5) Optimized fls() for T4 and above, from Vijay Kumar.

[PATCH] arm64: dts: sort vendor subdirectories in Makefile alphabetically

The list is almost sorted. Move "lg" up to complete it. Signed-off-by: Masahiro Yamada --- arch/arm64/boot/dts/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/Makefile b/arch/arm64/boot/dts/Makefile index

[PATCH] arm64: dts: sort vendor subdirectories in Makefile alphabetically

The list is almost sorted. Move "lg" up to complete it. Signed-off-by: Masahiro Yamada --- arch/arm64/boot/dts/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/Makefile b/arch/arm64/boot/dts/Makefile index d7c22d5..4aa50b9 100644 ---

Re: [Error after setting -Og] ‘__bad_copy_from’ declared with attribute error: copy source size is too small

On Thu, Nov 09, 2017 at 04:02:53PM -0500, Wei Wei wrote: > Hi all, > > I get a compile time error after setting -Og when compiling for the latest > GitHub version. > I am using `make defconfig’ to get the default x86_64 config. But previously > I did this in v4.4, > it's fine. ; cat >a.c

Re: [Error after setting -Og] ‘__bad_copy_from’ declared with attribute error: copy source size is too small

On Thu, Nov 09, 2017 at 04:02:53PM -0500, Wei Wei wrote: > Hi all, > > I get a compile time error after setting -Og when compiling for the latest > GitHub version. > I am using `make defconfig’ to get the default x86_64 config. But previously > I did this in v4.4, > it's fine. ; cat >a.c

Re: Fwd: FW: [PATCH 18/31] nds32: Library functions

On Tue, Nov 14, 2017 at 12:47:04PM +0800, Vincent Chen wrote: > Thanks > So, I should keep the area that we've copied into instead of zeroing > the area even if unpredicted exception is happened. Right? Yes. Here's what's required: if raw_copy_{from,to}_user(from, to, size) returns n, we want

Re: Fwd: FW: [PATCH 18/31] nds32: Library functions

On Tue, Nov 14, 2017 at 12:47:04PM +0800, Vincent Chen wrote: > Thanks > So, I should keep the area that we've copied into instead of zeroing > the area even if unpredicted exception is happened. Right? Yes. Here's what's required: if raw_copy_{from,to}_user(from, to, size) returns n, we want

[PATCH v2 08/13] nubus: Clean up whitespace

Tested-by: Stan Johnson Signed-off-by: Finn Thain --- include/linux/nubus.h | 54 +-- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/include/linux/nubus.h b/include/linux/nubus.h

[PATCH v2 01/13] nubus: Avoid array underflow and overflow

Check array indices. Avoid sprintf. Use buffers of sufficient size. Use appropriate types for array length parameters. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/nubus/nubus.c | 29 +

[PATCH v2 12/13] nubus: Add expansion_type values for various Mac models

Add an expansion slot attribute to allow drivers to properly handle cards like Comm Slot cards and PDS cards without declaration ROMs. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- arch/m68k/include/asm/macintosh.h | 9 ++-

[PATCH v2 03/13] nubus: Use static functions where possible

This fixes a couple of warnings from 'make W=1': drivers/nubus/nubus.c:790: warning: no previous prototype for 'nubus_probe_slot' drivers/nubus/nubus.c:824: warning: no previous prototype for 'nubus_scan_bus' Tested-by: Stan Johnson Signed-off-by: Finn Thain

[PATCH v2 08/13] nubus: Clean up whitespace

Tested-by: Stan Johnson Signed-off-by: Finn Thain --- include/linux/nubus.h | 54 +-- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/include/linux/nubus.h b/include/linux/nubus.h index 46e4d983feac..84f2e0fa1898 100644 ---

[PATCH v2 01/13] nubus: Avoid array underflow and overflow

Check array indices. Avoid sprintf. Use buffers of sufficient size. Use appropriate types for array length parameters. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/nubus/nubus.c | 29 + drivers/nubus/proc.c | 12 ++-- include/linux/nubus.h

[PATCH v2 12/13] nubus: Add expansion_type values for various Mac models

Add an expansion slot attribute to allow drivers to properly handle cards like Comm Slot cards and PDS cards without declaration ROMs. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- arch/m68k/include/asm/macintosh.h | 9 ++- arch/m68k/mac/config.c | 110

[PATCH v2 03/13] nubus: Use static functions where possible

This fixes a couple of warnings from 'make W=1': drivers/nubus/nubus.c:790: warning: no previous prototype for 'nubus_probe_slot' drivers/nubus/nubus.c:824: warning: no previous prototype for 'nubus_scan_bus' Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/nubus/nubus.c | 4 ++--

[PATCH v2 13/13] nubus: Add support for the driver model

This patch brings basic support for the Linux Driver Model to the NuBus subsystem. For flexibility, bus matching is left up to the drivers. This is also the approach taken by NetBSD NuBus drivers in matching cards. Since a board may have many functions, drivers have to consider all of a board's

[PATCH v2 04/13] nubus: Fix log spam

Testing shows that a single Radius PrecisionColor 24X display board, which has 95 functional resources, produces over a thousand lines of log messages. Suppress these messages with pr_debug(). Remove some redundant messages relating to nubus_get_subdir() calls. Fix the format block debug messages

[PATCH v2 10/13] nubus: Rework /proc/bus/nubus/s/ implementation

The /proc/bus/nubus/s/ directory tree for any slot s is missing a lot of information. The struct file_operations methods have long been left unimplemented (hence the familiar compile-time warning, "Need to set some I/O handlers here"). Slot resources have a complex structure which varies

[PATCH v2 09/13] nubus: Generalize block resource handling

Scrap the specialized code to unpack video mode name resources and driver resources. It isn't useful. Instead, add a re-usable function to handle lists of block resources of any kind, and descend into the mode table resource directory. Rename callers as nubus_get_foo(), consistent with their

[PATCH v2 11/13] nubus: Rename struct nubus_dev

It is misleading to call a functional resource a "device". In adopting the Linux Driver Model, struct nubus_board will embed a struct device. This will compound the problem because drivers will bind with boards, not with functional resources. Rename struct nubus_dev as struct nubus_rsrc.

[PATCH v2 13/13] nubus: Add support for the driver model

This patch brings basic support for the Linux Driver Model to the NuBus subsystem. For flexibility, bus matching is left up to the drivers. This is also the approach taken by NetBSD NuBus drivers in matching cards. Since a board may have many functions, drivers have to consider all of a board's

[PATCH v2 04/13] nubus: Fix log spam

Testing shows that a single Radius PrecisionColor 24X display board, which has 95 functional resources, produces over a thousand lines of log messages. Suppress these messages with pr_debug(). Remove some redundant messages relating to nubus_get_subdir() calls. Fix the format block debug messages

[PATCH v2 10/13] nubus: Rework /proc/bus/nubus/s/ implementation

The /proc/bus/nubus/s/ directory tree for any slot s is missing a lot of information. The struct file_operations methods have long been left unimplemented (hence the familiar compile-time warning, "Need to set some I/O handlers here"). Slot resources have a complex structure which varies

  1   2   3   4   5   6   7   8   9   10   >