Re: possible deadlock in blk_trace_remove

On 12/03/2017 01:24 PM, Eric Biggers wrote: > On Sun, Nov 19, 2017 at 02:36:01AM -0800, syzbot wrote: >> Hello, >> >> syzkaller hit the following crash on >> d9e0e63d9a6f88440eb201e1491fcf730272c706 >> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master >> compiler: gcc (GCC)

Re: possible deadlock in blk_trace_remove

On 12/03/2017 01:24 PM, Eric Biggers wrote: > On Sun, Nov 19, 2017 at 02:36:01AM -0800, syzbot wrote: >> Hello, >> >> syzkaller hit the following crash on >> d9e0e63d9a6f88440eb201e1491fcf730272c706 >> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master >> compiler: gcc (GCC)

Re: [PATCH v5.1 1/2] ARM64: dts: meson-gx: use stable UART bindings with correct gate clock

Am 03.12.2017 um 15:15 schrieb Andreas Färber: > Hi, > > Am 21.06.2017 um 16:42 schrieb Neil Armstrong: >> diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi >> b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi >> index 17d3efd..ea53cc2 100644 >> ---

Re: [PATCH v5.1 1/2] ARM64: dts: meson-gx: use stable UART bindings with correct gate clock

Am 03.12.2017 um 15:15 schrieb Andreas Färber: > Hi, > > Am 21.06.2017 um 16:42 schrieb Neil Armstrong: >> diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi >> b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi >> index 17d3efd..ea53cc2 100644 >> ---

Re: [PATCH] locking/Documentation: Revise Documentation/locking/crossrelease.txt

On Thu, Nov 16, 2017 at 08:22:37AM +0100, Ingo Molnar wrote: > > * Byungchul Park wrote: > > > On Sat, Nov 11, 2017 at 10:45:24PM +0900, Byungchul Park wrote: > > > This is the big one including all of version 3. > > > > > > You can take only this. > > > > Hello Ingo,

Re: [PATCH] locking/Documentation: Revise Documentation/locking/crossrelease.txt

On Thu, Nov 16, 2017 at 08:22:37AM +0100, Ingo Molnar wrote: > > * Byungchul Park wrote: > > > On Sat, Nov 11, 2017 at 10:45:24PM +0900, Byungchul Park wrote: > > > This is the big one including all of version 3. > > > > > > You can take only this. > > > > Hello Ingo, > > > > Could you

Re: [PATCH] leaking_addresses: add support for 32-bit kernel addresses

On Fri, Dec 01, 2017 at 06:39:07PM +0530, kaiwan.billimo...@gmail.com wrote: > Hi, > > Applies upon the previous one in this thread. > Found and fixed some minor issues with light testing on a 32-bit x86. > (I realize this isn't an ideal description, forgive me!). > > Have also emitted a 'noisy'

Re: [PATCH] leaking_addresses: add support for 32-bit kernel addresses

On Fri, Dec 01, 2017 at 06:39:07PM +0530, kaiwan.billimo...@gmail.com wrote: > Hi, > > Applies upon the previous one in this thread. > Found and fixed some minor issues with light testing on a 32-bit x86. > (I realize this isn't an ideal description, forgive me!). > > Have also emitted a 'noisy'

Re: [PATCH] fsi: Add Self Boot Engine FIFO FSI client

If there's enthusiasm for what I've proposed over Eddy and Brad's patch, I'll clean up the kbuild issues and resend. It was more meant to trigger discussion than sent as ready for submission. Cheers, Andrew On Mon, 4 Dec 2017, at 06:55, kbuild test robot wrote: > Hi Andrew, > > Thank you for

Re: [PATCH] fsi: Add Self Boot Engine FIFO FSI client

If there's enthusiasm for what I've proposed over Eddy and Brad's patch, I'll clean up the kbuild issues and resend. It was more meant to trigger discussion than sent as ready for submission. Cheers, Andrew On Mon, 4 Dec 2017, at 06:55, kbuild test robot wrote: > Hi Andrew, > > Thank you for

linux-next: build warning after merge of the net-next tree

Hi all, After merging the net-next tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: drivers/net/phy/broadcom.c:391:12: warning: 'bcm5482_read_status' defined but not used [-Wunused-function] static int bcm5482_read_status(struct phy_device *phydev) ^

linux-next: build warning after merge of the net-next tree

Hi all, After merging the net-next tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: drivers/net/phy/broadcom.c:391:12: warning: 'bcm5482_read_status' defined but not used [-Wunused-function] static int bcm5482_read_status(struct phy_device *phydev) ^

linux-next: Signed-off-by missing for commits in the drm tree

Hi all, There is a series of commits 54cff6479fd8 - c1802534e5a6 (not all in that range) that are missing a Signed-off-by from their committer. -- Cheers, Stephen Rothwell

linux-next: Signed-off-by missing for commits in the drm tree

Hi all, There is a series of commits 54cff6479fd8 - c1802534e5a6 (not all in that range) that are missing a Signed-off-by from their committer. -- Cheers, Stephen Rothwell

[PATCH] documentation/gpu/i915: fix docs build error after file rename

From: Randy Dunlap Fix documentation build errors after intel_guc_loader.c was renamed to intel_guc_fw.c. Error: Cannot open file ../drivers/gpu/drm/i915/intel_guc_loader.c WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno -function GuC-specific firmware

[PATCH] documentation/gpu/i915: fix docs build error after file rename

From: Randy Dunlap Fix documentation build errors after intel_guc_loader.c was renamed to intel_guc_fw.c. Error: Cannot open file ../drivers/gpu/drm/i915/intel_guc_loader.c WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno -function GuC-specific firmware loader

[PATCH v4] doc: add maintainer book

There is currently very little documentation in the kernel on maintainer level tasks. In particular there are no documents on creating pull requests to submit to Linus. Quoting Greg Kroah-Hartman on LKML: Anyway, this actually came up at the kernel summit / maintainer meeting a few weeks

[PATCH v4] doc: add maintainer book

There is currently very little documentation in the kernel on maintainer level tasks. In particular there are no documents on creating pull requests to submit to Linus. Quoting Greg Kroah-Hartman on LKML: Anyway, this actually came up at the kernel summit / maintainer meeting a few weeks

[PATCH] irqchip/gic-v3: Fix the driver probe() fail due to disabled GICC entry

As per MADT specification, it's perfectly valid firmware can pass MADT table to OS with disabled GICC entries. ARM64-SMP code skips those cpu cores to bring online. However the current GICv3 driver probe bails out in this case on systems where redistributor regions are not in the always-on power

[PATCH] irqchip/gic-v3: Fix the driver probe() fail due to disabled GICC entry

As per MADT specification, it's perfectly valid firmware can pass MADT table to OS with disabled GICC entries. ARM64-SMP code skips those cpu cores to bring online. However the current GICv3 driver probe bails out in this case on systems where redistributor regions are not in the always-on power

Re: [PATCH] treewide: remove duplicate includes

On Mon, 2017-12-04 at 03:19 +0530, Pravin Shedge wrote: > These duplicate includes have been found with scripts/checkincludes.pl but > they have been removed manually to avoid removing false positives. Can you list the duplicates that were not removed as well please?

Re: [PATCH] treewide: remove duplicate includes

On Mon, 2017-12-04 at 03:19 +0530, Pravin Shedge wrote: > These duplicate includes have been found with scripts/checkincludes.pl but > they have been removed manually to avoid removing false positives. Can you list the duplicates that were not removed as well please?

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'hva_to_pfn_slow': arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:1379:35: error: 'start' undeclared (first use in this function)

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'hva_to_pfn_slow': arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:1379:35: error: 'start' undeclared (first use in this function)

Re: [PATCH 1/4] arm: dts: imx28: Use phandles instead of unit addresses

Hi Ravi, Thank you for the patch! Yet something to improve: [auto build test ERROR on shawnguo/for-next] [also build test ERROR on v4.15-rc2 next-20171201] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 1/4] arm: dts: imx28: Use phandles instead of unit addresses

Hi Ravi, Thank you for the patch! Yet something to improve: [auto build test ERROR on shawnguo/for-next] [also build test ERROR on v4.15-rc2 next-20171201] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] treewide: remove duplicate includes

On Mon, Dec 04, 2017 at 03:19:39AM +0530, Pravin Shedge wrote: > These duplicate includes have been found with scripts/checkincludes.pl but > they have been removed manually to avoid removing false positives. > > Unit Testing: > > - build successful > - LTP testsuite passes. > - checkpatch.pl

Re: [PATCH] treewide: remove duplicate includes

On Mon, Dec 04, 2017 at 03:19:39AM +0530, Pravin Shedge wrote: > These duplicate includes have been found with scripts/checkincludes.pl but > they have been removed manually to avoid removing false positives. > > Unit Testing: > > - build successful > - LTP testsuite passes. > - checkpatch.pl

linux-next: manual merge of the vfs tree with Linus' tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in: drivers/net/ethernet/via/via-rhine.c between commit: a7e4fbbfdf79 ("net: via: via-rhine: use %p to format void * address instead of %x") from Linus' tree and commit: 68fef306c2a5 ("via: trivial sparse annotations")

linux-next: manual merge of the vfs tree with Linus' tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in: drivers/net/ethernet/via/via-rhine.c between commit: a7e4fbbfdf79 ("net: via: via-rhine: use %p to format void * address instead of %x") from Linus' tree and commit: 68fef306c2a5 ("via: trivial sparse annotations")

Re: [PATCH v4 07/12] [media] cxd2880: Add top level of the driver

Hello, Many thanks for the driver. The ./scripts/checkpatch.pl with --strict has many warnings, some of which might be nice to have cleaned up. There are some very minor comments below. Similar constructs are in other files too. After reading and understanding through all the code, I think

Re: [PATCH v4 07/12] [media] cxd2880: Add top level of the driver

Hello, Many thanks for the driver. The ./scripts/checkpatch.pl with --strict has many warnings, some of which might be nice to have cleaned up. There are some very minor comments below. Similar constructs are in other files too. After reading and understanding through all the code, I think

Re: [PATCH] [RFC] um: Convert ubd driver to blk-mq

On 03/12/17 21:54, Richard Weinberger wrote: > Christoph, > > Am Mittwoch, 29. November 2017, 22:46:51 CET schrieb Christoph Hellwig: >> On Sun, Nov 26, 2017 at 02:10:53PM +0100, Richard Weinberger wrote: >>> MAX_SG is 64, used for blk_queue_max_segments(). This comes from >>> a0044bdf60c2 ("uml:

Re: [PATCH] [RFC] um: Convert ubd driver to blk-mq

On 03/12/17 21:54, Richard Weinberger wrote: > Christoph, > > Am Mittwoch, 29. November 2017, 22:46:51 CET schrieb Christoph Hellwig: >> On Sun, Nov 26, 2017 at 02:10:53PM +0100, Richard Weinberger wrote: >>> MAX_SG is 64, used for blk_queue_max_segments(). This comes from >>> a0044bdf60c2 ("uml:

[PATCH v2] thinkad_acpi: Support the battery wear control

Add support for the ACPI batteries on newer thinkpad models (>Sandy Bridge) that support the setting of start and stop thresholds. The actual interface to the driver is a extension for the existing ACPI battery driver. This was done so that users can write transparently to the interface of the

[PATCH v2] thinkad_acpi: Support the battery wear control

Add support for the ACPI batteries on newer thinkpad models (>Sandy Bridge) that support the setting of start and stop thresholds. The actual interface to the driver is a extension for the existing ACPI battery driver. This was done so that users can write transparently to the interface of the

[PATCH] thinkad_acpi: Support the battery wear control

Add support for the ACPI batteries on newer thinkpad models (>Sandy Bridge) that support the setting of start and stop thresholds. The actual interface to the driver is a extension for the existing ACPI battery driver. This was done so that users can write transparently to the interface of the

[PATCH] thinkad_acpi: Support the battery wear control

Add support for the ACPI batteries on newer thinkpad models (>Sandy Bridge) that support the setting of start and stop thresholds. The actual interface to the driver is a extension for the existing ACPI battery driver. This was done so that users can write transparently to the interface of the

linux-next: manual merge of the samsung-krzk tree with the keystone tree

Hi Krzysztof, Today's linux-next merge of the samsung-krzk tree got a conflict in: arch/arm/configs/multi_v7_defconfig between commit: f15187dcdbcd ("ARM: config: sync multi-v7 config with keystone peripherals") from the keystone tree and commit: 453c63073185 ("ARM: multi_v7_defconfig:

linux-next: manual merge of the samsung-krzk tree with the keystone tree

Hi Krzysztof, Today's linux-next merge of the samsung-krzk tree got a conflict in: arch/arm/configs/multi_v7_defconfig between commit: f15187dcdbcd ("ARM: config: sync multi-v7 config with keystone peripherals") from the keystone tree and commit: 453c63073185 ("ARM: multi_v7_defconfig:

Re: [PATCH] frv: fix build failure

On Mon, Nov 27, 2017 at 10:25:16AM -0800, Vineet Gupta wrote: > +CC linux-arch, Arnd > > On 11/23/2017 09:17 AM, Alexey Brodkin wrote: > >Hi Sudip, > > > >On Tue, 2017-11-21 at 22:10 +, Sudip Mukherjee wrote: > I understand the case/need for adding a weak/common abort() as a > quick fix

Re: [PATCH] frv: fix build failure

On Mon, Nov 27, 2017 at 10:25:16AM -0800, Vineet Gupta wrote: > +CC linux-arch, Arnd > > On 11/23/2017 09:17 AM, Alexey Brodkin wrote: > >Hi Sudip, > > > >On Tue, 2017-11-21 at 22:10 +, Sudip Mukherjee wrote: > I understand the case/need for adding a weak/common abort() as a > quick fix

Re: [PATCH] Documentation: fix docs build error after source file removed

On Sun, 3 Dec 2017 13:15:39 -0800 Randy Dunlap wrote: > The pci/htirq.c file was removed so remove it from the documentation > file also. > > Error: Cannot open file ../drivers/pci/htirq.c > WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno -export >

Re: [PATCH] Documentation: fix docs build error after source file removed

On Sun, 3 Dec 2017 13:15:39 -0800 Randy Dunlap wrote: > The pci/htirq.c file was removed so remove it from the documentation > file also. > > Error: Cannot open file ../drivers/pci/htirq.c > WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno -export > ../drivers/pci/htirq.c' failed

[PATCH v3] ARM: da850: Fix LEGO EV3 battery voltage gpio

This fixes the battery voltage monitoring gpio-hog settings. When the gpio is low, it turns off the battery voltage to the ADC chip. However, this needs to be on all of the time so that we can monitor battery voltage. Also, there was a typo that prevented pinmuxing from working correctly.

[PATCH v3] ARM: da850: Fix LEGO EV3 battery voltage gpio

This fixes the battery voltage monitoring gpio-hog settings. When the gpio is low, it turns off the battery voltage to the ADC chip. However, this needs to be on all of the time so that we can monitor battery voltage. Also, there was a typo that prevented pinmuxing from working correctly.

Re: selftests: Testing a write attempt into a full file?

Am 03.12.2017 21:46, schrieb SF Markus Elfring: > Hello, > > I have constructed another demonstration program. > > > #include > #include > #include > > int main(void) > { > FILE *f = fopen("/dev/full", "a"); > > if (!f) > goto report_failure; > > { >

Re: selftests: Testing a write attempt into a full file?

Am 03.12.2017 21:46, schrieb SF Markus Elfring: > Hello, > > I have constructed another demonstration program. > > > #include > #include > #include > > int main(void) > { > FILE *f = fopen("/dev/full", "a"); > > if (!f) > goto report_failure; > > { >

[PATCH v2] ARM: da850: Fix LEGO EV3 battery voltage gpio

This fixes the battery voltage monitoring gpio-hog settings. When the gpio is low, it turns off the battery voltage to the ADC chip. However, this needs to be on all of the time so that we can monitor battery voltage. Also, there was a typo that prevented pinmuxing from working correctly.

[PATCH v2] ARM: da850: Fix LEGO EV3 battery voltage gpio

This fixes the battery voltage monitoring gpio-hog settings. When the gpio is low, it turns off the battery voltage to the ADC chip. However, this needs to be on all of the time so that we can monitor battery voltage. Also, there was a typo that prevented pinmuxing from working correctly.

Re: Difficulties for compilation without extra optimisation

> Why would you compile the kernel without optimization? I would like to see how big an effect finally is in such a build configuration after specific source code adjustments. > There's many places in the kernel that WILL NOT BUILD without optimization. I did not really know this detail so

Re: Difficulties for compilation without extra optimisation

> Why would you compile the kernel without optimization? I would like to see how big an effect finally is in such a build configuration after specific source code adjustments. > There's many places in the kernel that WILL NOT BUILD without optimization. I did not really know this detail so

Re: [PATCH] [RFC] um: Convert ubd driver to blk-mq

Christoph, Am Mittwoch, 29. November 2017, 22:46:51 CET schrieb Christoph Hellwig: > On Sun, Nov 26, 2017 at 02:10:53PM +0100, Richard Weinberger wrote: > > MAX_SG is 64, used for blk_queue_max_segments(). This comes from > > a0044bdf60c2 ("uml: batch I/O requests"). Is this still a good/sane > >

Re: [PATCH] [RFC] um: Convert ubd driver to blk-mq

Christoph, Am Mittwoch, 29. November 2017, 22:46:51 CET schrieb Christoph Hellwig: > On Sun, Nov 26, 2017 at 02:10:53PM +0100, Richard Weinberger wrote: > > MAX_SG is 64, used for blk_queue_max_segments(). This comes from > > a0044bdf60c2 ("uml: batch I/O requests"). Is this still a good/sane > >

[PATCH] treewide: remove duplicate includes

These duplicate includes have been found with scripts/checkincludes.pl but they have been removed manually to avoid removing false positives. Unit Testing: - build successful - LTP testsuite passes. - checkpatch.pl passes Signed-off-by: Pravin Shedge ---

[PATCH] treewide: remove duplicate includes

These duplicate includes have been found with scripts/checkincludes.pl but they have been removed manually to avoid removing false positives. Unit Testing: - build successful - LTP testsuite passes. - checkpatch.pl passes Signed-off-by: Pravin Shedge --- arch/arm/crypto/aes-ce-glue.c

[PATCH] um: Convert ubd driver to blk-mq

Convert the driver to the modern blk-mq framework. As byproduct we get rid of our open coded restart logic and let blk-mq handle it. Signed-off-by: Richard Weinberger --- arch/um/drivers/ubd_kern.c | 178 +++-- 1 file changed, 93

[PATCH] um: Convert ubd driver to blk-mq

Convert the driver to the modern blk-mq framework. As byproduct we get rid of our open coded restart logic and let blk-mq handle it. Signed-off-by: Richard Weinberger --- arch/um/drivers/ubd_kern.c | 178 +++-- 1 file changed, 93 insertions(+), 85

[PATCH] eeprom: at24: don't use the default regmap locking

We need to always wait for the last write to complete and we want the regmap to be protected from concurrent access during that wait. That makes using the regmap's default locking impossible and we're protecting it with an external mutex. Set an empty function as the callback for regmap's lock

[PATCH] eeprom: at24: don't use the default regmap locking

We need to always wait for the last write to complete and we want the regmap to be protected from concurrent access during that wait. That makes using the regmap's default locking impossible and we're protecting it with an external mutex. Set an empty function as the callback for regmap's lock

[PATCH] i2c: core: report OF style module alias for devices registered via OF

The buses should honor the firmware interface used to register the device, but the I2C core reports a MODALIAS of the form i2c: even for I2C devices registered via OF. This means that user-space will never get an OF stype uevent MODALIAS even when the drivers modules contain aliases exported from

[PATCH] i2c: core: report OF style module alias for devices registered via OF

The buses should honor the firmware interface used to register the device, but the I2C core reports a MODALIAS of the form i2c: even for I2C devices registered via OF. This means that user-space will never get an OF stype uevent MODALIAS even when the drivers modules contain aliases exported from

linux-next: Signed-off-by missing for commit in the arm-soc tree

Hi all, Commit 5f56b7f4854a ("Revert "Merge tag 'scpi-updates-4.15' of git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux into next/drivers"") is missing a Signed-off-by from its author or committer. Reverts are commits as well and so need an explanation of why they are done

linux-next: Signed-off-by missing for commit in the arm-soc tree

Hi all, Commit 5f56b7f4854a ("Revert "Merge tag 'scpi-updates-4.15' of git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux into next/drivers"") is missing a Signed-off-by from its author or committer. Reverts are commits as well and so need an explanation of why they are done

Re: Difficulties for compilation without extra optimisation

On Sun, 3 Dec 2017 15:17:32 + Trond Myklebust wrote: > > I would like to check corresponding build results then without extra > > optimisation applied by the compiler. > > But I got surprised by error messages for a command like the > > following. > > > >

Re: Difficulties for compilation without extra optimisation

On Sun, 3 Dec 2017 15:17:32 + Trond Myklebust wrote: > > I would like to check corresponding build results then without extra > > optimisation applied by the compiler. > > But I got surprised by error messages for a command like the > > following. > > > >

Make SSB a menuconfig to ease disabling it all

The following patch makes it easier to disable all SSB config options without entering the submenu. It will also enable one to see that en-disabled state from the outside menu. This is only intended to change menuconfig UI, not change the config dependencies.

[PATCH] Make SSB a menuconfig to ease disabling it all

No need to get into the submenu to disable all SSB-related config entries Signed-off-by: Vincent Legoll --- drivers/ssb/Kconfig | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/ssb/Kconfig b/drivers/ssb/Kconfig index

Make SSB a menuconfig to ease disabling it all

The following patch makes it easier to disable all SSB config options without entering the submenu. It will also enable one to see that en-disabled state from the outside menu. This is only intended to change menuconfig UI, not change the config dependencies.

[PATCH] Make SSB a menuconfig to ease disabling it all

No need to get into the submenu to disable all SSB-related config entries Signed-off-by: Vincent Legoll --- drivers/ssb/Kconfig | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/ssb/Kconfig b/drivers/ssb/Kconfig index d8e4219c2324..f48a2ee587a4 100644 ---

[PATCH] sched/core: fix kernel-doc warnings after code movement

From: Randy Dunlap Fix kernel-doc warnings after code restructuring. ../kernel/sched/core.c:5113: warning: No description found for parameter 't' ../kernel/sched/core.c:5113: warning: Excess function parameter 'interval' description in 'sched_rr_get_interval' Fixes:

[PATCH] sched/core: fix kernel-doc warnings after code movement

From: Randy Dunlap Fix kernel-doc warnings after code restructuring. ../kernel/sched/core.c:5113: warning: No description found for parameter 't' ../kernel/sched/core.c:5113: warning: Excess function parameter 'interval' description in 'sched_rr_get_interval' Fixes: abca5fc535a3e

[PATCH] Documentation: fix docs build error after source file removed

From: Randy Dunlap The pci/htirq.c file was removed so remove it from the documentation file also. Error: Cannot open file ../drivers/pci/htirq.c WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno -export ../drivers/pci/htirq.c' failed with return code 2

[PATCH] Documentation: fix docs build error after source file removed

From: Randy Dunlap The pci/htirq.c file was removed so remove it from the documentation file also. Error: Cannot open file ../drivers/pci/htirq.c WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno -export ../drivers/pci/htirq.c' failed with return code 2 Fixes: fd2fa6c18b72

[PATCH] mm/memory.c: Mark wp_huge_pmd() inline to prevent build failure

With gcc 4.1.2: mm/memory.o: In function `wp_huge_pmd': memory.c:(.text+0x9b4): undefined reference to `do_huge_pmd_wp_page' Interestingly, wp_huge_pmd() is emitted in the assembler output, but never called. Apparently replacing the call to pmd_write() in __handle_mm_fault() by a call

[PATCH] mm/memory.c: Mark wp_huge_pmd() inline to prevent build failure

With gcc 4.1.2: mm/memory.o: In function `wp_huge_pmd': memory.c:(.text+0x9b4): undefined reference to `do_huge_pmd_wp_page' Interestingly, wp_huge_pmd() is emitted in the assembler output, but never called. Apparently replacing the call to pmd_write() in __handle_mm_fault() by a call

Re: [PATCH] leds: trigger: Introduce a NETDEV trigger

Hi Ben, Thanks for the patch. I have some comments in the code below. Please take a look. On 11/28/2017 10:54 PM, Ben Whitten wrote: > This commit introduces a NETDEV trigger for named device > activity. Available triggers are link, rx, and tx. > > Signed-off-by: Ben Whitten

Re: [PATCH] leds: trigger: Introduce a NETDEV trigger

Hi Ben, Thanks for the patch. I have some comments in the code below. Please take a look. On 11/28/2017 10:54 PM, Ben Whitten wrote: > This commit introduces a NETDEV trigger for named device > activity. Available triggers are link, rx, and tx. > > Signed-off-by: Ben Whitten > --- >

Re: [PATCH 1/2] dt-bindings: trivial: add tfa9879 device

On Sun, Dec 3, 2017 at 6:53 PM, Peter Rosin wrote: > That's funny, because I get the below on both 4.14 and 4.15-rc1. And I > expect the same ever since the driver was added some 3 years ago. > > $ scripts/get_maintainer.pl your-patch-from[1].diff | grep Peter > Peter Rosin

Re: [PATCH 1/2] dt-bindings: trivial: add tfa9879 device

On Sun, Dec 3, 2017 at 6:53 PM, Peter Rosin wrote: > That's funny, because I get the below on both 4.14 and 4.15-rc1. And I > expect the same ever since the driver was added some 3 years ago. > > $ scripts/get_maintainer.pl your-patch-from[1].diff | grep Peter > Peter Rosin (maintainer:NXP

Re: [PATCH 1/2] dt-bindings: trivial: add tfa9879 device

On 2017-12-03 12:12, Fabio Estevam wrote: > Hi Peter, > > On Sun, Dec 3, 2017 at 4:59 AM, Peter Rosin wrote: > >> Right. However, the patch adding that should have been sent to me, the >> maintainer of the driver. That is carefully recorded in MAINTAINERS. So, >> forgive me for

Re: [PATCH 1/2] dt-bindings: trivial: add tfa9879 device

On 2017-12-03 12:12, Fabio Estevam wrote: > Hi Peter, > > On Sun, Dec 3, 2017 at 4:59 AM, Peter Rosin wrote: > >> Right. However, the patch adding that should have been sent to me, the >> maintainer of the driver. That is carefully recorded in MAINTAINERS. So, >> forgive me for assuming that

selftests: Testing a write attempt into a full file?

Hello, I have constructed another demonstration program. #include #include #include int main(void) { FILE *f = fopen("/dev/full", "a"); if (!f) goto report_failure; { int const c = 'X'; if (fputc(c, f) != c) goto

selftests: Testing a write attempt into a full file?

Hello, I have constructed another demonstration program. #include #include #include int main(void) { FILE *f = fopen("/dev/full", "a"); if (!f) goto report_failure; { int const c = 'X'; if (fputc(c, f) != c) goto

Re: [PATCH 3/5] PCI: cadence: Add host driver for Cadence PCIe controller

Hi Lorenzo, Le 29/11/2017 à 18:34, Lorenzo Pieralisi a écrit : > On Thu, Nov 23, 2017 at 04:01:48PM +0100, Cyrille Pitchen wrote: >> This patch adds support to the Cadence PCIe controller in host mode. > > Bjorn already commented on this, it would be good to add some > of the cover letter

Re: [PATCH 3/5] PCI: cadence: Add host driver for Cadence PCIe controller

Hi Lorenzo, Le 29/11/2017 à 18:34, Lorenzo Pieralisi a écrit : > On Thu, Nov 23, 2017 at 04:01:48PM +0100, Cyrille Pitchen wrote: >> This patch adds support to the Cadence PCIe controller in host mode. > > Bjorn already commented on this, it would be good to add some > of the cover letter

Re: general protection fault in dax_alloc_inode

On Tue, Nov 14, 2017 at 04:46:01AM -0800, syzbot wrote: > RBP: R08: R09: > R10: R11: R12: > R13: R14: R15: > kasan: CONFIG_KASAN_INLINE enabled >

Re: general protection fault in dax_alloc_inode

On Tue, Nov 14, 2017 at 04:46:01AM -0800, syzbot wrote: > RBP: R08: R09: > R10: R11: R12: > R13: R14: R15: > kasan: CONFIG_KASAN_INLINE enabled >

Re: kernel BUG at net/key/af_key.c:LINE!

On Wed, Nov 15, 2017 at 12:29:19PM +0100, Steffen Klassert wrote: > On Fri, Nov 10, 2017 at 02:14:06PM +1100, Herbert Xu wrote: > > On Fri, Nov 10, 2017 at 01:30:38PM +1100, Herbert Xu wrote: > > > > > > I found the problem. This crap is coming from clone_policy. Now > > > let me where this

Re: kernel BUG at net/key/af_key.c:LINE!

On Wed, Nov 15, 2017 at 12:29:19PM +0100, Steffen Klassert wrote: > On Fri, Nov 10, 2017 at 02:14:06PM +1100, Herbert Xu wrote: > > On Fri, Nov 10, 2017 at 01:30:38PM +1100, Herbert Xu wrote: > > > > > > I found the problem. This crap is coming from clone_policy. Now > > > let me where this

Re: [PATCH v2] NTB: ntb_pp: Add full multi-port NTB API support

Hi Serge, I love your patch! Yet something to improve: [auto build test ERROR on v4.15-rc1] [cannot apply to ntb/ntb-next next-20171201] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2] NTB: ntb_pp: Add full multi-port NTB API support

Hi Serge, I love your patch! Yet something to improve: [auto build test ERROR on v4.15-rc1] [cannot apply to ntb/ntb-next next-20171201] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] fsi: Add Self Boot Engine FIFO FSI client

Hi Andrew, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.15-rc2 next-20171201] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] fsi: Add Self Boot Engine FIFO FSI client

Hi Andrew, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.15-rc2 next-20171201] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: possible deadlock in blk_trace_remove

On Sun, Nov 19, 2017 at 02:36:01AM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > d9e0e63d9a6f88440eb201e1491fcf730272c706 > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console

Re: possible deadlock in blk_trace_remove

On Sun, Nov 19, 2017 at 02:36:01AM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > d9e0e63d9a6f88440eb201e1491fcf730272c706 > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console

Re: WARNING in kmalloc_slab (3)

+Cc linux-block On Sun, Dec 03, 2017 at 06:25:01AM -0800, syzbot wrote: > WARNING: CPU: 0 PID: 3081 at mm/slab_common.c:971 kmalloc_slab+0x5d/0x70 > mm/slab_common.c:971 > Kernel panic - not syncing: panic_on_warn set ... > [...] > __do_kmalloc mm/slab.c:3706 [inline] > __kmalloc+0x25/0x760

Re: WARNING in kmalloc_slab (3)

+Cc linux-block On Sun, Dec 03, 2017 at 06:25:01AM -0800, syzbot wrote: > WARNING: CPU: 0 PID: 3081 at mm/slab_common.c:971 kmalloc_slab+0x5d/0x70 > mm/slab_common.c:971 > Kernel panic - not syncing: panic_on_warn set ... > [...] > __do_kmalloc mm/slab.c:3706 [inline] > __kmalloc+0x25/0x760

[PATCH] netfilter: nfnetlink_cthelper: Add missing permission checks

The capability check in nfnetlink_rcv() verifies that the caller has CAP_NET_ADMIN in the namespace that "owns" the netlink socket. However, nfnl_cthelper_list is shared by all net namespaces on the system. An unprivileged user can create user and net namespaces in which he holds CAP_NET_ADMIN to

[PATCH] netfilter: nfnetlink_cthelper: Add missing permission checks

The capability check in nfnetlink_rcv() verifies that the caller has CAP_NET_ADMIN in the namespace that "owns" the netlink socket. However, nfnl_cthelper_list is shared by all net namespaces on the system. An unprivileged user can create user and net namespaces in which he holds CAP_NET_ADMIN to

<    1   2   3   4   5   6   7   >