[PATCH v4 2/4] ACPICA: Tables: Add mechanism to allow to balance late stage acpi_get_table() independently

For all frequent late stage acpi_get_table() clone invocations, we should only change them altogether, otherwise, excessive acpi_put_table() could unexpectedly unmap the table used by the other users. Thus the current plan is to change all acpi_get_table() clones together or to change none of

[PATCH v4 2/4] ACPICA: Tables: Add mechanism to allow to balance late stage acpi_get_table() independently

For all frequent late stage acpi_get_table() clone invocations, we should only change them altogether, otherwise, excessive acpi_put_table() could unexpectedly unmap the table used by the other users. Thus the current plan is to change all acpi_get_table() clones together or to change none of

[PATCH v4 1/3] KASLR: Parse all memmap entries in cmdline

In commit: f28442497b5c ("x86/boot: Fix KASLR and memmap= collision") ... the memmap= option is parsed so that KASLR can avoid those reserved regions. It uses cmdline_find_option() to get the value if memmap= is specified, however the problem is that cmdline_find_option() can only find the

[PATCH v4 3/4] ACPI: sysfs: Fix acpi_get_table() leak

From: Dan Williams Reading an ACPI table through the /sys/firmware/acpi/tables interface more than 65,536 times leads to the following log message: ACPI Error: Table 88033595eaa8, Validation count is zero after increment (20170119/tbutils-423) Add the missing

[PATCH v4 1/3] KASLR: Parse all memmap entries in cmdline

In commit: f28442497b5c ("x86/boot: Fix KASLR and memmap= collision") ... the memmap= option is parsed so that KASLR can avoid those reserved regions. It uses cmdline_find_option() to get the value if memmap= is specified, however the problem is that cmdline_find_option() can only find the

[PATCH v4 3/4] ACPI: sysfs: Fix acpi_get_table() leak

From: Dan Williams Reading an ACPI table through the /sys/firmware/acpi/tables interface more than 65,536 times leads to the following log message: ACPI Error: Table 88033595eaa8, Validation count is zero after increment (20170119/tbutils-423) Add the missing acpi_put_table() so the

[PATCH v4 2/3] KASLR: Handle memory limit specified by memmap and mem option

Option mem= will limit the max address a system can use and any memory region above the limit will be removed. Furthermore, memmap=nn[KMG] which has no offset specified has the same behaviour as mem=. KASLR needs to consider this when choosing the random position for decompressing the kernel.

[PATCH v4 3/3] Documentation/kernel-parameters.txt: Update 'memmap=' option description

In commit: 9710f581bb4c ("x86, mm: Let "memmap=" take more entries one time") ... 'memmap=' was changed to adopt multiple, comma delimited values in a single entry, so update the related description. In the special case of only specifying size value without an offset, like memmap=nn[KMG],

[PATCH v4 2/3] KASLR: Handle memory limit specified by memmap and mem option

Option mem= will limit the max address a system can use and any memory region above the limit will be removed. Furthermore, memmap=nn[KMG] which has no offset specified has the same behaviour as mem=. KASLR needs to consider this when choosing the random position for decompressing the kernel.

[PATCH v4 3/3] Documentation/kernel-parameters.txt: Update 'memmap=' option description

In commit: 9710f581bb4c ("x86, mm: Let "memmap=" take more entries one time") ... 'memmap=' was changed to adopt multiple, comma delimited values in a single entry, so update the related description. In the special case of only specifying size value without an offset, like memmap=nn[KMG],

[PATCH v4 4/4] ACPI: Fix memory mapping leaks in current sysfs dumpable ACPI tables support

This patch adds acpi_put_table() to make all acpi_get_table() clone invocations balanced for sysfs ACPI table dump code. Since Linux does not use all of the tables, this can help to reduce some usless memory mappings. While originally, all tables will be remained to be mapped after a userspace

[PATCH v4 4/4] ACPI: Fix memory mapping leaks in current sysfs dumpable ACPI tables support

This patch adds acpi_put_table() to make all acpi_get_table() clone invocations balanced for sysfs ACPI table dump code. Since Linux does not use all of the tables, this can help to reduce some usless memory mappings. While originally, all tables will be remained to be mapped after a userspace

[PATCH v4 0/3] Handle memmap and mem kernel options in boot stage kaslr

People reported kernel panic occurs during system boots up with mem boot option. After checking code, several problems are found about memmap= and mem= in boot stage kaslr. *) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"), only one memmap entry is considered and only

[PATCH v4 0/3] Handle memmap and mem kernel options in boot stage kaslr

People reported kernel panic occurs during system boots up with mem boot option. After checking code, several problems are found about memmap= and mem= in boot stage kaslr. *) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"), only one memmap entry is considered and only

[PATCH v4 1/4] ACPICA: Tables: Fix regression introduced by a too early mechanism enabling

In the Linux kernel side, acpi_get_table() clones haven't been fully balanced by acpi_put_table() invocations. In ACPICA side, due to the design change, there are also unbalanced acpi_get_table_by_index() invocations requiring special care. So it is not a good timing to report acpi_get_table()

[PATCH v4 1/4] ACPICA: Tables: Fix regression introduced by a too early mechanism enabling

In the Linux kernel side, acpi_get_table() clones haven't been fully balanced by acpi_put_table() invocations. In ACPICA side, due to the design change, there are also unbalanced acpi_get_table_by_index() invocations requiring special care. So it is not a good timing to report acpi_get_table()

Re: [PATCH] mfd: cros-ec: Add cros_ec_readmem() helpers for I2C/SPI based ECs

Hi Moritz, [auto build test WARNING on ljones-mfd/for-mfd-next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] mfd: cros-ec: Add cros_ec_readmem() helpers for I2C/SPI based ECs

Hi Moritz, [auto build test WARNING on ljones-mfd/for-mfd-next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2 3/3] fs: ubifs: set s_uuid in super block

On 05/09/2017 07:37 AM, Amir Goldstein wrote: On Tue, May 9, 2017 at 7:13 AM, Oleksij Rempel > wrote: On 05/02/2017 09:37 AM, Richard Weinberger wrote: Amir, Am 02.05.2017 um 09:19 schrieb Amir Goldstein:

Re: [PATCH v2 3/3] fs: ubifs: set s_uuid in super block

On 05/09/2017 07:37 AM, Amir Goldstein wrote: On Tue, May 9, 2017 at 7:13 AM, Oleksij Rempel mailto:o...@pengutronix.de>> wrote: On 05/02/2017 09:37 AM, Richard Weinberger wrote: Amir, Am 02.05.2017 um 09:19 schrieb Amir Goldstein: On Fri, Apr 28, 2017

lening bieden

Goede dag,  Dit is het beveiligingsnetwerk van de kredietverstrekking.   SAFETY NET CREDIT biedt flexibele en betaalbare leningen voor elk doel om u te helpen uw doelen te bereiken. We lenen tegen een lage rente van 3%. Hier zijn enkele belangrijke kenmerken van de persoonlijke lening

lening bieden

Goede dag,  Dit is het beveiligingsnetwerk van de kredietverstrekking.   SAFETY NET CREDIT biedt flexibele en betaalbare leningen voor elk doel om u te helpen uw doelen te bereiken. We lenen tegen een lage rente van 3%. Hier zijn enkele belangrijke kenmerken van de persoonlijke lening

Re: sky2: Use seq_putc() in sky2_debug_show()

On Mon, 8 May 2017 19:42:46 +0200 SF Markus Elfring wrote: > > Which issue do you mean? I dont see any issue you fix here. > > Are the run time characteristics a bit nicer for the function “seq_putc” > in comparison to the function “seq_puts” for printing a

Re: sky2: Use seq_putc() in sky2_debug_show()

On Mon, 8 May 2017 19:42:46 +0200 SF Markus Elfring wrote: > > Which issue do you mean? I dont see any issue you fix here. > > Are the run time characteristics a bit nicer for the function “seq_putc” > in comparison to the function “seq_puts” for printing a single line break > here? > >

Re: [PATCH] dt-bindings: power: New bindings for ltc3651-charger

On 08-05-17 19:12, Rob Herring wrote: On Fri, May 05, 2017 at 08:38:35AM +0200, Mike Looijmans wrote: This adds the devicetree bindings documentation for the LTC3651 battery charger. Signed-off-by: Mike Looijmans --- .../bindings/power/supply/ltc3651-charger.txt

Re: [PATCH] dt-bindings: power: New bindings for ltc3651-charger

On 08-05-17 19:12, Rob Herring wrote: On Fri, May 05, 2017 at 08:38:35AM +0200, Mike Looijmans wrote: This adds the devicetree bindings documentation for the LTC3651 battery charger. Signed-off-by: Mike Looijmans --- .../bindings/power/supply/ltc3651-charger.txt | 26

[PATCH v3] power: Add ltc3651-charger driver

The LTC3651 reports its status via GPIO lines. This driver translates the GPIO levels to battery charger status information via sysfs. It relies on devicetree to supply the IO configuration. Signed-off-by: Mike Looijmans --- v3: Add "lltc" vendor prefix to DT gpios

[PATCH v3] power: Add ltc3651-charger driver

The LTC3651 reports its status via GPIO lines. This driver translates the GPIO levels to battery charger status information via sysfs. It relies on devicetree to supply the IO configuration. Signed-off-by: Mike Looijmans --- v3: Add "lltc" vendor prefix to DT gpios properties v2: Remove unused

Re: CFP: KVM Forum 2017

On 05/02/2017 06:41 AM, Paolo Bonzini wrote: > > KVM Forum 2017: Call For Participation > October 25-27, 2017 - Hilton Prague - Prague, Czech Republic > > (All submissions must be received before midnight June 15, 2017) >

Re: CFP: KVM Forum 2017

On 05/02/2017 06:41 AM, Paolo Bonzini wrote: > > KVM Forum 2017: Call For Participation > October 25-27, 2017 - Hilton Prague - Prague, Czech Republic > > (All submissions must be received before midnight June 15, 2017) >

Re: [PATCH] driver core: platform: Add ability to find resource by name or index

On Mon, May 08, 2017 at 05:59:48PM -0400, Jon Mason wrote: > It is not always possible to find a resource via the name. This may be > due to using previous versions of device tree without the names or using > ACPI. To allow for resources to be discovered by either the name or the > index, a

Re: [PATCH] driver core: platform: Add ability to find resource by name or index

On Mon, May 08, 2017 at 05:59:48PM -0400, Jon Mason wrote: > It is not always possible to find a resource via the name. This may be > due to using previous versions of device tree without the names or using > ACPI. To allow for resources to be discovered by either the name or the > index, a

Re: [PATCH] misc: Implement devm_misc_register

On Tue, May 09, 2017 at 02:27:48AM +, Gregory Fong wrote: > Add device managed devm_misc_register() to allow simplifying some > miscdevice code. > > Signed-off-by: Gregory Fong > --- > This seemed like it would be handy for removing a large chunk of the cleanup

Re: [PATCH] misc: Implement devm_misc_register

On Tue, May 09, 2017 at 02:27:48AM +, Gregory Fong wrote: > Add device managed devm_misc_register() to allow simplifying some > miscdevice code. > > Signed-off-by: Gregory Fong > --- > This seemed like it would be handy for removing a large chunk of the cleanup > code in various miscdevice

[PATCH] net: fec: select queue depending on VLAN priority

Since the addition of the multi queue code with commit 59d0f7465644 ("net: fec: init multi queue date structure") the queue selection has been handelt by the default transmit queue selection implementation which tries to evenly distribute the traffic across all available queues. This selection

[PATCH] net: fec: select queue depending on VLAN priority

Since the addition of the multi queue code with commit 59d0f7465644 ("net: fec: init multi queue date structure") the queue selection has been handelt by the default transmit queue selection implementation which tries to evenly distribute the traffic across all available queues. This selection

[PATCH v2] dt-bindings: power: New bindings for ltc3651-charger

This adds the devicetree bindings documentation for the LTC3651 battery charger. Signed-off-by: Mike Looijmans --- v2: Add "lltc," vendor prefix to gpios Expand irq paragraph .../bindings/power/supply/ltc3651-charger.txt | 27 ++ 1 file

[PATCH v2] dt-bindings: power: New bindings for ltc3651-charger

This adds the devicetree bindings documentation for the LTC3651 battery charger. Signed-off-by: Mike Looijmans --- v2: Add "lltc," vendor prefix to gpios Expand irq paragraph .../bindings/power/supply/ltc3651-charger.txt | 27 ++ 1 file changed, 27 insertions(+)

[git pull] vfs.git misc stuff

Assorted bits and pieces from various people. No common topic in that pile, sorry. The following changes since commit 4f7d029b9bf009fbee76bb10c0c4351a1870d2f3: Linux 4.11-rc7 (2017-04-16 13:00:18 -0700) are available in the git repository at:

[git pull] vfs.git misc stuff

Assorted bits and pieces from various people. No common topic in that pile, sorry. The following changes since commit 4f7d029b9bf009fbee76bb10c0c4351a1870d2f3: Linux 4.11-rc7 (2017-04-16 13:00:18 -0700) are available in the git repository at:

Re: [PATCH] net: wireless: ath: ath10k: remove unnecessary code

"Gustavo A. R. Silva" writes: > The name of an array used by itself will always return the array's address. > So these tests will always evaluate as false and therefore the _return_ > will never be executed. > > Signed-off-by: Gustavo A. R. Silva

Re: [PATCH] net: wireless: ath: ath10k: remove unnecessary code

"Gustavo A. R. Silva" writes: > The name of an array used by itself will always return the array's address. > So these tests will always evaluate as false and therefore the _return_ > will never be executed. > > Signed-off-by: Gustavo A. R. Silva I don't understand the commit log, especially

[git pull] vfs.git fix

Braino fix for iov_iter_revert() misuse The following changes since commit a6a5993243550b09f620941dea741b7421fdf79c: iov_iter: don't revert iov buffer if csum error (2017-05-01 14:49:53 -0400) are available in the git repository at:

Re: [greybus-dev] [PATCH v2] Staging: greybus: light: Prefer kcalloc over kzalloc

On 08-05-17, 18:05, kart...@techveda.org wrote: > From: Karthik Tummala > > Fixed following checkpatch.pl warning: > * WARNING: Prefer kcalloc over kzalloc with multiply > > Instead of specifying no.of bytes * size as argument > in kzalloc, prefer kcalloc. > >

[git pull] vfs.git fix

Braino fix for iov_iter_revert() misuse The following changes since commit a6a5993243550b09f620941dea741b7421fdf79c: iov_iter: don't revert iov buffer if csum error (2017-05-01 14:49:53 -0400) are available in the git repository at:

Re: [greybus-dev] [PATCH v2] Staging: greybus: light: Prefer kcalloc over kzalloc

On 08-05-17, 18:05, kart...@techveda.org wrote: > From: Karthik Tummala > > Fixed following checkpatch.pl warning: > * WARNING: Prefer kcalloc over kzalloc with multiply > > Instead of specifying no.of bytes * size as argument > in kzalloc, prefer kcalloc. > > Signed-off-by: Karthik Tummala

Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property

On 08-05-17, 14:57, Sudeep Holla wrote: > Yes, I followed the thread and figured that out. But Rajendra also > raised "What if the microcontroller firmware maps the performance-index > to voltage but expects linux to scale the frequency? There is no way to > specify a performance-index *and* a

Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property

On 08-05-17, 14:57, Sudeep Holla wrote: > Yes, I followed the thread and figured that out. But Rajendra also > raised "What if the microcontroller firmware maps the performance-index > to voltage but expects linux to scale the frequency? There is no way to > specify a performance-index *and* a

sound/core/hwdep_compat.c:43:31: sparse: incorrect type in argument 2 (different address spaces)

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: bf5f89463f5b3109a72ed13ca62b57e90213387d commit: beba3a20bf90ce1b93e24592c3ebf0d0bb581bbe x86: switch to RAW_COPY_USER date: 6 weeks ago reproduce: # apt-get install sparse git checkout

sound/core/hwdep_compat.c:43:31: sparse: incorrect type in argument 2 (different address spaces)

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: bf5f89463f5b3109a72ed13ca62b57e90213387d commit: beba3a20bf90ce1b93e24592c3ebf0d0bb581bbe x86: switch to RAW_COPY_USER date: 6 weeks ago reproduce: # apt-get install sparse git checkout

[PATCH] rpmsg: Make rpmsg_create_ept() propagate error

Make the rpmsg_create_ept() return an ERR_PTR() rather than NULL, as this is common practice throughout the kernel and I got the first two clients of this API wrong. Signed-off-by: Bjorn Andersson --- drivers/rpmsg/qcom_smd.c | 8

[PATCH] rpmsg: Make rpmsg_create_ept() propagate error

Make the rpmsg_create_ept() return an ERR_PTR() rather than NULL, as this is common practice throughout the kernel and I got the first two clients of this API wrong. Signed-off-by: Bjorn Andersson --- drivers/rpmsg/qcom_smd.c | 8 drivers/rpmsg/rpmsg_char.c | 4 ++--

Re: [PATCH 3/3] arm64/locking: qspinlocks and qrwlocks support

On Wed, May 03, 2017 at 05:51:41PM +0300, Yury Norov wrote: > From: Jan Glauber > > Ported from x86_64 with paravirtualization support removed. > > Signed-off-by: Jan Glauber > > Note. This patch removes protection from direct inclusion of >

Re: [PATCH 3/3] arm64/locking: qspinlocks and qrwlocks support

On Wed, May 03, 2017 at 05:51:41PM +0300, Yury Norov wrote: > From: Jan Glauber > > Ported from x86_64 with paravirtualization support removed. > > Signed-off-by: Jan Glauber > > Note. This patch removes protection from direct inclusion of > arch/arm64/include/asm/spinlock_types.h. It's done

[PATCH] mfd: intel_quark_i2c_gpio: Add support for SIMATIC IOT2000 platform

The SIMATIC IOT2000 is derived from the Galileo Gen2 board and shares its I2C frequency. Signed-off-by: Jan Kiszka Signed-off-by: Sascha Weisenberger --- drivers/mfd/intel_quark_i2c_gpio.c | 4 1 file changed, 4 insertions(+) diff

[PATCH] mfd: intel_quark_i2c_gpio: Add support for SIMATIC IOT2000 platform

The SIMATIC IOT2000 is derived from the Galileo Gen2 board and shares its I2C frequency. Signed-off-by: Jan Kiszka Signed-off-by: Sascha Weisenberger --- drivers/mfd/intel_quark_i2c_gpio.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/mfd/intel_quark_i2c_gpio.c

[PATCH] wcn36xx: Close SMD channel on device removal

The SMD channel is not the primary WCNSS channel and must explicitly be closed as the device is removed, or the channel will already by open on a subsequent probe call in e.g. the case of reloading the kernel module. This issue was introduced because I simplified the underlying SMD implementation

[PATCH] wcn36xx: Close SMD channel on device removal

The SMD channel is not the primary WCNSS channel and must explicitly be closed as the device is removed, or the channel will already by open on a subsequent probe call in e.g. the case of reloading the kernel module. This issue was introduced because I simplified the underlying SMD implementation

[PATCH] net: wireless: ath: ath10k: remove unnecessary code

The name of an array used by itself will always return the array's address. So these tests will always evaluate as false and therefore the _return_ will never be executed. Signed-off-by: Gustavo A. R. Silva --- drivers/net/wireless/ath/ath10k/wmi.c | 9 - 1 file

[PATCH] net: wireless: ath: ath10k: remove unnecessary code

The name of an array used by itself will always return the array's address. So these tests will always evaluate as false and therefore the _return_ will never be executed. Signed-off-by: Gustavo A. R. Silva --- drivers/net/wireless/ath/ath10k/wmi.c | 9 - 1 file changed, 9 deletions(-)

Re: [PATCH 0/4] DMA-buf: Fine-tuning for four function implementations

Hello Markus, On 8 May 2017 at 14:40, SF Markus Elfring wrote: > From: Markus Elfring > Date: Mon, 8 May 2017 11:05:05 +0200 > > A few update suggestions were taken into account > from static source code analysis. > > Markus Elfring

Re: [PATCH 0/4] DMA-buf: Fine-tuning for four function implementations

Hello Markus, On 8 May 2017 at 14:40, SF Markus Elfring wrote: > From: Markus Elfring > Date: Mon, 8 May 2017 11:05:05 +0200 > > A few update suggestions were taken into account > from static source code analysis. > > Markus Elfring (4): > Combine two function calls into one in

[regression, bisected] 4.11+ imx uarts broken

Hi, The following commit e61c38d85b7 makes the uarts on i.MX6 nonfunctional (no data transmitted or received). With e61c38d85b7 reverted the uarts work ok. --- commit e61c38d85b7392e033ee03bca46f1d6006156175 Author: Uwe Kleine-König Date: Tue

[regression, bisected] 4.11+ imx uarts broken

Hi, The following commit e61c38d85b7 makes the uarts on i.MX6 nonfunctional (no data transmitted or received). With e61c38d85b7 reverted the uarts work ok. --- commit e61c38d85b7392e033ee03bca46f1d6006156175 Author: Uwe Kleine-König Date: Tue Apr 4 11:18:51 2017 +0200

Re: [PATCH v2 3/3] fs: ubifs: set s_uuid in super block

On 05/02/2017 09:37 AM, Richard Weinberger wrote: Amir, Am 02.05.2017 um 09:19 schrieb Amir Goldstein: On Fri, Apr 28, 2017 at 1:03 AM, Richard Weinberger wrote: Am 24.04.2017 um 17:47 schrieb Richard Weinberger: So, if some flag should be implemented, who should do it? :)

Re: [PATCH v2 3/3] fs: ubifs: set s_uuid in super block

On 05/02/2017 09:37 AM, Richard Weinberger wrote: Amir, Am 02.05.2017 um 09:19 schrieb Amir Goldstein: On Fri, Apr 28, 2017 at 1:03 AM, Richard Weinberger wrote: Am 24.04.2017 um 17:47 schrieb Richard Weinberger: So, if some flag should be implemented, who should do it? :) I'll not do

[PATCH] net: wireless: ath: ath9k: remove unnecessary code

The name of an array used by itself will always return the array's address. So this test will always evaluate as true. Addresses-Coverity-ID: 1364903 Signed-off-by: Gustavo A. R. Silva --- drivers/net/wireless/ath/ath9k/eeprom.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH] net: wireless: ath: ath9k: remove unnecessary code

The name of an array used by itself will always return the array's address. So this test will always evaluate as true. Addresses-Coverity-ID: 1364903 Signed-off-by: Gustavo A. R. Silva --- drivers/net/wireless/ath/ath9k/eeprom.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

linux-next: Tree for May 9

Hi all, Please do not add any v4.13 destined material in your linux-next included branches until after v4.12-rc1 has been released. Changes since 20170508: Non-merge commits (relative to Linus' tree): 2374 2523 files changed, 83999 insertions(+), 42709 deletions

linux-next: Tree for May 9

Hi all, Please do not add any v4.13 destined material in your linux-next included branches until after v4.12-rc1 has been released. Changes since 20170508: Non-merge commits (relative to Linus' tree): 2374 2523 files changed, 83999 insertions(+), 42709 deletions

Re: [PATCH 40/40] media: imx: set and propagate empty field, colorimetry params

On 05/08/2017 02:41 AM, Philipp Zabel wrote: Hi Steve, On Wed, 2017-04-12 at 17:45 -0700, Steve Longerbeam wrote: This patch adds a call to imx_media_fill_empty_mbus_fields() in the *_try_fmt() functions at the sink pads, to set empty field order and colorimetry parameters. If the field

Re: [PATCH 40/40] media: imx: set and propagate empty field, colorimetry params

On 05/08/2017 02:41 AM, Philipp Zabel wrote: Hi Steve, On Wed, 2017-04-12 at 17:45 -0700, Steve Longerbeam wrote: This patch adds a call to imx_media_fill_empty_mbus_fields() in the *_try_fmt() functions at the sink pads, to set empty field order and colorimetry parameters. If the field

Re: [Patch v4] x86/build: don't add -maccumulate-outgoing-args w/o compiler support

On Mon, May 08, 2017 at 08:29:46PM -0700, Nick Desaulniers wrote: > Clang does not support this machine dependent option. > > Older versions of GCC (pre 3.0) may not support this option, added in > 2000, but it's unlikely they can still compile the kernel. > > Signed-off-by: Nick Desaulniers

Re: [Patch v4] x86/build: don't add -maccumulate-outgoing-args w/o compiler support

On Mon, May 08, 2017 at 08:29:46PM -0700, Nick Desaulniers wrote: > Clang does not support this machine dependent option. > > Older versions of GCC (pre 3.0) may not support this option, added in > 2000, but it's unlikely they can still compile the kernel. > > Signed-off-by: Nick Desaulniers >

Re: [PATCH 7/7] DWARF: add the config option

On Mon, May 08, 2017 at 07:31:50PM -0700, Andy Lutomirski wrote: > On Mon, May 8, 2017 at 6:38 PM, Josh Poimboeuf wrote: > >> Also, don't you need some indication of which reg is the base from > >> which you find previous frame? After all, sometimes GCC will emit a > >>

Re: [PATCH 7/7] DWARF: add the config option

On Mon, May 08, 2017 at 07:31:50PM -0700, Andy Lutomirski wrote: > On Mon, May 8, 2017 at 6:38 PM, Josh Poimboeuf wrote: > >> Also, don't you need some indication of which reg is the base from > >> which you find previous frame? After all, sometimes GCC will emit a > >> frame pointer even in an

Re: [PATCH] thermal: core: make thermal_emergency_poweroff static

On Monday 08 May 2017 04:06 PM, Colin King wrote: > From: Colin Ian King > > Making thermal_emergency_poweroff static fixes sparse warning: > > drivers/thermal/thermal_core.c:6: warning: symbol > 'thermal_emergency_poweroff' was not declared. Should it be static?

Re: [PATCH] thermal: core: make thermal_emergency_poweroff static

On Monday 08 May 2017 04:06 PM, Colin King wrote: > From: Colin Ian King > > Making thermal_emergency_poweroff static fixes sparse warning: > > drivers/thermal/thermal_core.c:6: warning: symbol > 'thermal_emergency_poweroff' was not declared. Should it be static? Acked-by: Keerthy > >

Re: [PATCH v2] x86/efi: Correct ident mapping of efi old_map when kalsr enabled

On 05/08/17 at 05:25pm, Borislav Petkov wrote: > On Mon, May 08, 2017 at 09:36:49AM +0800, Baoquan He wrote: > > Thanks for explaining, Bhupesh. > > > > BIOS issue of SGI uv1 is still not fixed. There's a quirk for uv1 to > > use efi old map: > > > > void __init efi_apply_memmap_quirks(void) >

Re: [PATCH v2] x86/efi: Correct ident mapping of efi old_map when kalsr enabled

On 05/08/17 at 05:25pm, Borislav Petkov wrote: > On Mon, May 08, 2017 at 09:36:49AM +0800, Baoquan He wrote: > > Thanks for explaining, Bhupesh. > > > > BIOS issue of SGI uv1 is still not fixed. There's a quirk for uv1 to > > use efi old map: > > > > void __init efi_apply_memmap_quirks(void) >

[Patch v4] x86/build: don't add -maccumulate-outgoing-args w/o compiler support

Clang does not support this machine dependent option. Older versions of GCC (pre 3.0) may not support this option, added in 2000, but it's unlikely they can still compile the kernel. Signed-off-by: Nick Desaulniers --- arch/x86/Makefile | 3 ++- 1 file changed, 2

[Patch v4] x86/build: don't add -maccumulate-outgoing-args w/o compiler support

Clang does not support this machine dependent option. Older versions of GCC (pre 3.0) may not support this option, added in 2000, but it's unlikely they can still compile the kernel. Signed-off-by: Nick Desaulniers --- arch/x86/Makefile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)

net/xfrm/xfrm_input.c:84:9: sparse: context imbalance in 'xfrm_rcv_cb' - unexpected unlock

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: bf5f89463f5b3109a72ed13ca62b57e90213387d commit: 960fdfdeb9e85a67bed136bc945c541ba61c2bdd xfrm: input: constify xfrm_input_afinfo date: 3 months ago reproduce: # apt-get install sparse git

net/xfrm/xfrm_input.c:84:9: sparse: context imbalance in 'xfrm_rcv_cb' - unexpected unlock

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: bf5f89463f5b3109a72ed13ca62b57e90213387d commit: 960fdfdeb9e85a67bed136bc945c541ba61c2bdd xfrm: input: constify xfrm_input_afinfo date: 3 months ago reproduce: # apt-get install sparse git

Re: [PATCH] scsi: qedf: properly update arguments position in function call

Hi Martin, Quoting "Martin K. Petersen" : Gustavo A., Properly update the position of the arguments in function call. Applied to 4.12/scsi-fixes, thank you! Awesome, glad to help. :) -- Gustavo A. R. Silva

Re: [PATCH] scsi: qedf: properly update arguments position in function call

Hi Martin, Quoting "Martin K. Petersen" : Gustavo A., Properly update the position of the arguments in function call. Applied to 4.12/scsi-fixes, thank you! Awesome, glad to help. :) -- Gustavo A. R. Silva

Re: [PATCH v8 2/7] doc: Add documentation for Coresight CPU debug

Hi Mathieu, On Wed, May 03, 2017 at 04:29:37PM -0600, Mathieu Poirier wrote: > On Tue, May 02, 2017 at 06:08:32PM +0800, Leo Yan wrote: > > Update kernel-parameters.txt to add new parameter: > > coresight_cpu_debug.enable is a knob to enable debugging at boot time. > > > > Add detailed

Re: [PATCH v8 2/7] doc: Add documentation for Coresight CPU debug

Hi Mathieu, On Wed, May 03, 2017 at 04:29:37PM -0600, Mathieu Poirier wrote: > On Tue, May 02, 2017 at 06:08:32PM +0800, Leo Yan wrote: > > Update kernel-parameters.txt to add new parameter: > > coresight_cpu_debug.enable is a knob to enable debugging at boot time. > > > > Add detailed

[PATCH v9 5/9] coresight: of_get_coresight_platform_data: Add missing of_node_put

From: Suzuki K Poulose The of_get_coresight_platform_data iterates over the possible CPU nodes to find a given cpu phandle. However it does not drop the reference to the node pointer returned by the of_get_coresight_platform_data. This patch also introduces another minor

[PATCH v9 5/9] coresight: of_get_coresight_platform_data: Add missing of_node_put

From: Suzuki K Poulose The of_get_coresight_platform_data iterates over the possible CPU nodes to find a given cpu phandle. However it does not drop the reference to the node pointer returned by the of_get_coresight_platform_data. This patch also introduces another minor fix is to use

[PATCH v9 9/9] arm64: dts: qcom: msm8916: Add debug unit

Add debug unit on Qualcomm msm8916 based platforms, including the DragonBoard 410c board. Signed-off-by: Leo Yan --- arch/arm64/boot/dts/qcom/msm8916.dtsi | 32 1 file changed, 32 insertions(+) diff --git

[PATCH v9 9/9] arm64: dts: qcom: msm8916: Add debug unit

Add debug unit on Qualcomm msm8916 based platforms, including the DragonBoard 410c board. Signed-off-by: Leo Yan --- arch/arm64/boot/dts/qcom/msm8916.dtsi | 32 1 file changed, 32 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/msm8916.dtsi

[PATCH v9 8/9] arm64: dts: hi6220: register debug module

Bind debug module driver for Hi6220. Signed-off-by: Leo Yan --- arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 64 +++ 1 file changed, 64 insertions(+) diff --git a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi

[PATCH v9 7/9] coresight: add support for CPU debug module

Coresight includes debug module and usually the module connects with CPU debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has description for related info in "Part H: External Debug". Chapter H7 "The Sample-based Profiling Extension" introduces several sampling registers, e.g.

[PATCH v9 6/9] coresight: refactor with function of_coresight_get_cpu

This is refactor to add function of_coresight_get_cpu(), so it's used to retrieve CPU id for coresight component. Finally can use it as a common function for multiple places. Suggested-by: Mathieu Poirier Reviewed-by: Suzuki K Poulose

[PATCH v9 8/9] arm64: dts: hi6220: register debug module

Bind debug module driver for Hi6220. Signed-off-by: Leo Yan --- arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 64 +++ 1 file changed, 64 insertions(+) diff --git a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi b/arch/arm64/boot/dts/hisilicon/hi6220.dtsi index

[PATCH v9 7/9] coresight: add support for CPU debug module

Coresight includes debug module and usually the module connects with CPU debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has description for related info in "Part H: External Debug". Chapter H7 "The Sample-based Profiling Extension" introduces several sampling registers, e.g.

[PATCH v9 6/9] coresight: refactor with function of_coresight_get_cpu

This is refactor to add function of_coresight_get_cpu(), so it's used to retrieve CPU id for coresight component. Finally can use it as a common function for multiple places. Suggested-by: Mathieu Poirier Reviewed-by: Suzuki K Poulose Signed-off-by: Leo Yan ---

[PATCH v9 4/9] MAINTAINERS: update file entries for Coresight subsystem

Update document file entries for Coresight debug module. Signed-off-by: Leo Yan --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index b948dfa..a4b1f60 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -1191,7 +1191,9 @@ L:

[PATCH v9 3/9] doc: Add coresight_cpu_debug.enable to kernel-parameters.txt

Add coresight_cpu_debug.enable to kernel-parameters.txt, this flag is used to enable/disable the CPU sampling based debugging. Signed-off-by: Leo Yan --- Documentation/admin-guide/kernel-parameters.txt | 7 +++ 1 file changed, 7 insertions(+) diff --git

  1   2   3   4   5   6   7   8   9   10   >