Re: [PATCH v4 5/8] bus: fsl-mc: dpio: add QBMan portal APIs for DPAA2

Hi Roy, [auto build test ERROR on staging/staging-testing] [also build test ERROR on next-20161215] [cannot apply to v4.9] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Stuart-Yoder/staging

Re: [PATCH v4 5/8] bus: fsl-mc: dpio: add QBMan portal APIs for DPAA2

Hi Roy, [auto build test ERROR on staging/staging-testing] [also build test ERROR on next-20161215] [cannot apply to v4.9] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Stuart-Yoder/staging

Re: default 0 if KASAN expression not working in kbuild

On 16.12.2016 09:50, Nikolay Borisov wrote: > > > On 15.12.2016 23:32, Randy Dunlap wrote: >> On 12/15/16 10:09, Nikolay Borisov wrote: >>> Hello, >>> >>> I was doing some kasan-related debugging and when I enabled it I started >>> getting warnings for large stackframes. So CONFIG_FRAME_WARN

Re: [PATCH v5 1/6] [media] rc-main: assign driver type during allocation

Hi Andi, [auto build test ERROR on linuxtv-media/master] [cannot apply to v4.9 next-20161215] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Andi-Shyti/Add-support-for-IR-transmitters/20161216

Re: default 0 if KASAN expression not working in kbuild

On 16.12.2016 09:50, Nikolay Borisov wrote: > > > On 15.12.2016 23:32, Randy Dunlap wrote: >> On 12/15/16 10:09, Nikolay Borisov wrote: >>> Hello, >>> >>> I was doing some kasan-related debugging and when I enabled it I started >>> getting warnings for large stackframes. So CONFIG_FRAME_WARN

Re: [PATCH v5 1/6] [media] rc-main: assign driver type during allocation

Hi Andi, [auto build test ERROR on linuxtv-media/master] [cannot apply to v4.9 next-20161215] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Andi-Shyti/Add-support-for-IR-transmitters/20161216

[PATCH 2/2] arm64: dts: Add dts files for Hisilicon Hi3660 SoC

Add initial dtsi file to support Hisilicon Hi3660 SoC with support of Octal core CPUs in two clusters(4 * A53 & 4 * A73). Also add dts file to support HiKey960 development board which based on Hi3660 SoC. The output console is earlycon "earlycon=pl011,0xfdf05000". And the con_init uart5 with a

[PATCH 2/2] arm64: dts: Add dts files for Hisilicon Hi3660 SoC

Add initial dtsi file to support Hisilicon Hi3660 SoC with support of Octal core CPUs in two clusters(4 * A53 & 4 * A73). Also add dts file to support HiKey960 development board which based on Hi3660 SoC. The output console is earlycon "earlycon=pl011,0xfdf05000". And the con_init uart5 with a

Re: default 0 if KASAN expression not working in kbuild

On 15.12.2016 23:32, Randy Dunlap wrote: > On 12/15/16 10:09, Nikolay Borisov wrote: >> Hello, >> >> I was doing some kasan-related debugging and when I enabled it I started >> getting warnings for large stackframes. So CONFIG_FRAME_WARN has : >> >> int "Warn for stack frames larger than (needs

Re: default 0 if KASAN expression not working in kbuild

On 15.12.2016 23:32, Randy Dunlap wrote: > On 12/15/16 10:09, Nikolay Borisov wrote: >> Hello, >> >> I was doing some kasan-related debugging and when I enabled it I started >> getting warnings for large stackframes. So CONFIG_FRAME_WARN has : >> >> int "Warn for stack frames larger than (needs

Re: [RFC 01/10] kmod: add test driver to stress test the module loader

On Tue, Dec 13, 2016 at 10:10:41PM +0100, Luis R. Rodriguez wrote: > On Thu, Dec 08, 2016 at 12:24:35PM -0800, Kees Cook wrote: > > On Thu, Dec 8, 2016 at 10:47 AM, Luis R. Rodriguez > > wrote: > > > 3) finit_module() consumes quite a bit of memory. > > > > Is this due to

Re: [RFC 01/10] kmod: add test driver to stress test the module loader

On Tue, Dec 13, 2016 at 10:10:41PM +0100, Luis R. Rodriguez wrote: > On Thu, Dec 08, 2016 at 12:24:35PM -0800, Kees Cook wrote: > > On Thu, Dec 8, 2016 at 10:47 AM, Luis R. Rodriguez > > wrote: > > > 3) finit_module() consumes quite a bit of memory. > > > > Is this due to reading the module

Re: OOM: Better, but still there on 4.9

[CC linux-mm and btrfs guys] On Thu 15-12-16 23:57:04, Nils Holland wrote: [...] > Of course, none of this are workloads that are new / special in any > way - prior to 4.8, I never experienced any issues doing the exact > same things. > > Dec 15 19:02:16 teela kernel: kworker/u4:5 invoked

Re: OOM: Better, but still there on 4.9

[CC linux-mm and btrfs guys] On Thu 15-12-16 23:57:04, Nils Holland wrote: [...] > Of course, none of this are workloads that are new / special in any > way - prior to 4.8, I never experienced any issues doing the exact > same things. > > Dec 15 19:02:16 teela kernel: kworker/u4:5 invoked

Re: [PATCH] ARM: dts: Add missing CPU frequencies for Exynos5422/5800

On Thu, Dec 15, 2016 at 04:52:58PM -0800, Doug Anderson wrote: > > [ I added Arjun to Cc:, maybe he can help in explaining this issue > > (unfortunately Inderpal's email is no longer working). ] > > > > Please also note that on Exynos5422/5800 SoCs the same ARM rail > > voltage is used for 1.9

Re: [PATCH] ARM: dts: Add missing CPU frequencies for Exynos5422/5800

On Thu, Dec 15, 2016 at 04:52:58PM -0800, Doug Anderson wrote: > > [ I added Arjun to Cc:, maybe he can help in explaining this issue > > (unfortunately Inderpal's email is no longer working). ] > > > > Please also note that on Exynos5422/5800 SoCs the same ARM rail > > voltage is used for 1.9

Re: [PATCH] kref: prefer atomic_inc_not_zero to atomic_add_unless

On Thu, Dec 15, 2016 at 11:10:49AM -0800, Greg KH wrote: > On Thu, Dec 15, 2016 at 07:55:54PM +0100, Jason A. Donenfeld wrote: > > On most platforms, there exists this ifdef: > > > > #define atomic_inc_not_zero(v) atomic_add_unless((v), 1, 0) > > > > This makes this patch functionally useless.

Re: [PATCH] kref: prefer atomic_inc_not_zero to atomic_add_unless

On Thu, Dec 15, 2016 at 11:10:49AM -0800, Greg KH wrote: > On Thu, Dec 15, 2016 at 07:55:54PM +0100, Jason A. Donenfeld wrote: > > On most platforms, there exists this ifdef: > > > > #define atomic_inc_not_zero(v) atomic_add_unless((v), 1, 0) > > > > This makes this patch functionally useless.

Re: Can't boot as Xen dom0 due to commit fe055896

On 15/12/16 18:36, Borislav Petkov wrote: > On Thu, Dec 15, 2016 at 12:27:49PM -0500, Boris Ostrovsky wrote: >> It will probably fix it but I don't think we want this: it's a >> build-time solution. Most kernels have XEN on even though they are >> booted bare-metal. > > Lemme tell you want I

Re: Can't boot as Xen dom0 due to commit fe055896

On 15/12/16 18:36, Borislav Petkov wrote: > On Thu, Dec 15, 2016 at 12:27:49PM -0500, Boris Ostrovsky wrote: >> It will probably fix it but I don't think we want this: it's a >> build-time solution. Most kernels have XEN on even though they are >> booted bare-metal. > > Lemme tell you want I

Re: wl1251 & mac address & calibration data

On 12/16/2016 03:03 AM, Luis R. Rodriguez wrote: For the new API a solution for "fallback mechanisms" should be clean though and I am looking to stay as far as possible from the existing mess. A solution to help both the old API and new API is possible for the "fallback mechanism" though -- but

Re: wl1251 & mac address & calibration data

On 12/16/2016 03:03 AM, Luis R. Rodriguez wrote: For the new API a solution for "fallback mechanisms" should be clean though and I am looking to stay as far as possible from the existing mess. A solution to help both the old API and new API is possible for the "fallback mechanism" though -- but

Re: [PATCH v4 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info

On Friday 16 December 2016 12:16 AM, Peter Zijlstra wrote: On Fri, Dec 16, 2016 at 12:07:06AM +0530, Hari Bathini wrote: +struct perf_ns_link_info { + __u64 dev; + __u64 ino; +}; + +enum { + NET_NS_INDEX= 0, + UTS_NS_INDEX= 1, +

Re: [PATCH v4 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info

On Friday 16 December 2016 12:16 AM, Peter Zijlstra wrote: On Fri, Dec 16, 2016 at 12:07:06AM +0530, Hari Bathini wrote: +struct perf_ns_link_info { + __u64 dev; + __u64 ino; +}; + +enum { + NET_NS_INDEX= 0, + UTS_NS_INDEX= 1, +

[PATCH] fs: fix a typo in fs/compat.c

Fix a typo in fs/compat.c Signed-off-by: Yanchuan Nian --- fs/compat.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/compat.c b/fs/compat.c index 6af20de..a6d6a4a 100644 --- a/fs/compat.c +++ b/fs/compat.c @@ -1,7 +1,7 @@ /* * linux/fs/compat.c *

[PATCH] fs: fix a typo in fs/compat.c

Fix a typo in fs/compat.c Signed-off-by: Yanchuan Nian --- fs/compat.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/compat.c b/fs/compat.c index 6af20de..a6d6a4a 100644 --- a/fs/compat.c +++ b/fs/compat.c @@ -1,7 +1,7 @@ /* * linux/fs/compat.c * - * Kernel

[PATCH RFC] liquidio: make timeout HZ independent

schedule_timeout_* takes a timeout in jiffies but the code currently is passing in a constant which makes this timeout HZ dependent, so pass it through msecs_to_jiffies() to fix this up. Fixes: commit b0d66369edcd ("liquidio VF error handling") Signed-off-by: Nicholas Mc Guire

[PATCH RFC] liquidio: make timeout HZ independent

schedule_timeout_* takes a timeout in jiffies but the code currently is passing in a constant which makes this timeout HZ dependent, so pass it through msecs_to_jiffies() to fix this up. Fixes: commit b0d66369edcd ("liquidio VF error handling") Signed-off-by: Nicholas Mc Guire --- Problem found

[GIT PULL] s390 patches for 4.10 merge window #2

Hi Linus, please pull from the 'for-linus' branch of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus to receive the following updates: Over 95% of the changes in this pull request are related to the zcrypt driver. There are five improvements for zcrypt: the ID

[GIT PULL] s390 patches for 4.10 merge window #2

Hi Linus, please pull from the 'for-linus' branch of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus to receive the following updates: Over 95% of the changes in this pull request are related to the zcrypt driver. There are five improvements for zcrypt: the ID

[PATCH] Btrfs: add another missing end_page_writeback on submit_extent_page failure

This is actually inspired by Filipe's patch(55e3bd2e0c2e1). When submit_extent_page() in __extent_writepage_io() fails, Btrfs misses clearing a writeback bit of the failed page. This causes the false under-writeback page. Then, another sync task hangs in filemap_fdatawait_range(), because it

[PATCH] Btrfs: add another missing end_page_writeback on submit_extent_page failure

This is actually inspired by Filipe's patch(55e3bd2e0c2e1). When submit_extent_page() in __extent_writepage_io() fails, Btrfs misses clearing a writeback bit of the failed page. This causes the false under-writeback page. Then, another sync task hangs in filemap_fdatawait_range(), because it

Re: jemalloc testsuite stalls in memset

Hello, On Thu, Dec 15, 2016 at 10:24:47AM +0100, Andreas Schwab wrote: > On Dez 15 2016, Minchan Kim wrote: > > > You mean program itself access the address(ie, 0xb740) is hang > > while access the address from the debugger is OK? > > Yes. > > > Can you reproduce

Re: jemalloc testsuite stalls in memset

Hello, On Thu, Dec 15, 2016 at 10:24:47AM +0100, Andreas Schwab wrote: > On Dez 15 2016, Minchan Kim wrote: > > > You mean program itself access the address(ie, 0xb740) is hang > > while access the address from the debugger is OK? > > Yes. > > > Can you reproduce it easily? > > 100%

Re: [PATCH v2 2/5] ia64: reuse append_elf_note() and final_note() functions

On Saturday 03 December 2016 12:52 AM, Eric W. Biederman wrote: Hari Bathini writes: Hi Dave, Thanks for the review. On Thursday 01 December 2016 10:26 AM, Dave Young wrote: Hi Hari Personally I like V1 more, but split the patch 2 is easier for ia64 people

Re: [PATCH v2 2/5] ia64: reuse append_elf_note() and final_note() functions

On Saturday 03 December 2016 12:52 AM, Eric W. Biederman wrote: Hari Bathini writes: Hi Dave, Thanks for the review. On Thursday 01 December 2016 10:26 AM, Dave Young wrote: Hi Hari Personally I like V1 more, but split the patch 2 is easier for ia64 people to reivew. I did basic x86

[PATCH] powerpc/livepatch: Remove klp_write_module_reloc() stub

commit 425595a7fc20 ("livepatch: reuse module loader code to write relocations") offloads livepatch module relocation write to arch specific module loader code. Remove unused klp_write_module_reloc() function stub. Signed-off-by: Kamalesh Babulal ---

[PATCH] powerpc/livepatch: Remove klp_write_module_reloc() stub

commit 425595a7fc20 ("livepatch: reuse module loader code to write relocations") offloads livepatch module relocation write to arch specific module loader code. Remove unused klp_write_module_reloc() function stub. Signed-off-by: Kamalesh Babulal --- arch/powerpc/include/asm/livepatch.h | 7

[PATCH v5 6/6] [media] rc: add support for IR LEDs driven through SPI

The ir-spi is a simple device driver which supports the connection between an IR LED and the MOSI line of an SPI device. The driver, indeed, uses the SPI framework to stream the raw data provided by userspace through an rc character device. The chardev is handled by the LIRC framework and its

[PATCH v5 4/6] [media] rc-ir-raw: do not generate any receiving thread for raw transmitters

Raw IR transmitters do not need any thread listening for occurring events. Check the driver type before running the thread. Signed-off-by: Andi Shyti Reviewed-by: Sean Young --- drivers/media/rc/rc-ir-raw.c | 17 - 1 file changed, 12

[PATCH v5 6/6] [media] rc: add support for IR LEDs driven through SPI

The ir-spi is a simple device driver which supports the connection between an IR LED and the MOSI line of an SPI device. The driver, indeed, uses the SPI framework to stream the raw data provided by userspace through an rc character device. The chardev is handled by the LIRC framework and its

[PATCH v5 4/6] [media] rc-ir-raw: do not generate any receiving thread for raw transmitters

Raw IR transmitters do not need any thread listening for occurring events. Check the driver type before running the thread. Signed-off-by: Andi Shyti Reviewed-by: Sean Young --- drivers/media/rc/rc-ir-raw.c | 17 - 1 file changed, 12 insertions(+), 5 deletions(-) diff --git

[PATCH v5 3/6] [media] rc-core: add support for IR raw transmitters

IR raw transmitter driver type is specified in the enum rc_driver_type as RC_DRIVER_IR_RAW_TX which includes all those devices that transmit raw stream of bit to a receiver. The data are provided by userspace applications, therefore they don't need any input device allocation, but still they need

[PATCH v5 5/6] Documentation: bindings: add documentation for ir-spi device driver

Document the ir-spi driver's binding which is a IR led driven through the SPI line. Signed-off-by: Andi Shyti Reviewed-by: Sean Young --- .../devicetree/bindings/leds/irled/spi-ir-led.txt | 29 ++ 1 file changed, 29 insertions(+)

[PATCH v5 2/6] [media] rc-main: split setup and unregister functions

Move the input device allocation, map and protocol handling to different functions. Signed-off-by: Andi Shyti Reviewed-by: Sean Young --- drivers/media/rc/rc-main.c | 143 + 1 file changed, 81 insertions(+), 62

[PATCH v5 5/6] Documentation: bindings: add documentation for ir-spi device driver

Document the ir-spi driver's binding which is a IR led driven through the SPI line. Signed-off-by: Andi Shyti Reviewed-by: Sean Young --- .../devicetree/bindings/leds/irled/spi-ir-led.txt | 29 ++ 1 file changed, 29 insertions(+) create mode 100644

[PATCH v5 2/6] [media] rc-main: split setup and unregister functions

Move the input device allocation, map and protocol handling to different functions. Signed-off-by: Andi Shyti Reviewed-by: Sean Young --- drivers/media/rc/rc-main.c | 143 + 1 file changed, 81 insertions(+), 62 deletions(-) diff --git

[PATCH v5 3/6] [media] rc-core: add support for IR raw transmitters

IR raw transmitter driver type is specified in the enum rc_driver_type as RC_DRIVER_IR_RAW_TX which includes all those devices that transmit raw stream of bit to a receiver. The data are provided by userspace applications, therefore they don't need any input device allocation, but still they need

[PATCH v5 1/6] [media] rc-main: assign driver type during allocation

The driver type can be assigned immediately when an RC device requests to the framework to allocate the device. This is an 'enum rc_driver_type' data type and specifies whether the device is a raw receiver or scancode receiver. The type will be given as parameter to the rc_allocate_device device.

[PATCH v5 0/6] Add support for IR transmitters

Hi, The main goal is to add support in the rc framework for IR transmitters, which currently is only supported by lirc but that is not the preferred way. The last patch adds support for an IR transmitter driven by the MOSI line of an SPI controller, it's the case of the Samsung TM2(e) board

[PATCH v5 1/6] [media] rc-main: assign driver type during allocation

The driver type can be assigned immediately when an RC device requests to the framework to allocate the device. This is an 'enum rc_driver_type' data type and specifies whether the device is a raw receiver or scancode receiver. The type will be given as parameter to the rc_allocate_device device.

[PATCH v5 0/6] Add support for IR transmitters

Hi, The main goal is to add support in the rc framework for IR transmitters, which currently is only supported by lirc but that is not the preferred way. The last patch adds support for an IR transmitter driven by the MOSI line of an SPI controller, it's the case of the Samsung TM2(e) board

Re: [PATCH] printk: Remove no longer used second struct cont

On Thu, 2016-12-15 at 21:00 -0800, Junio C Hamano wrote: > Joe Perches writes: > > > grep 2.5.4 was the last version that supported the -P option to > > grep through for multiple lines. > > Does anybody know why it was dropped? perl compatible regexes in grep have always been

Re: [PATCH] printk: Remove no longer used second struct cont

On Thu, 2016-12-15 at 21:00 -0800, Junio C Hamano wrote: > Joe Perches writes: > > > grep 2.5.4 was the last version that supported the -P option to > > grep through for multiple lines. > > Does anybody know why it was dropped? perl compatible regexes in grep have always been "experimental"

[PATCH] PM / devfreq: Fix the wrong description for userspace governor

This patch fixes the wrong description of governor_userspace.c and removes the unneeded blank line. Signed-off-by: Chanwoo Choi --- drivers/devfreq/governor_userspace.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH] PM / devfreq: Fix the wrong description for userspace governor

This patch fixes the wrong description of governor_userspace.c and removes the unneeded blank line. Signed-off-by: Chanwoo Choi --- drivers/devfreq/governor_userspace.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/devfreq/governor_userspace.c

Re: [RFC PATCH v2] crypto: Add IV generation algorithms

Hi Milan, On 13 December 2016 at 15:31, Milan Broz wrote: > I think that IV generators should not modify or read encrypted data directly, > it should only generate IV. I was trying to find more information about what you said and how a iv generator should be written. I saw

Re: [RFC PATCH v2] crypto: Add IV generation algorithms

Hi Milan, On 13 December 2016 at 15:31, Milan Broz wrote: > I think that IV generators should not modify or read encrypted data directly, > it should only generate IV. I was trying to find more information about what you said and how a iv generator should be written. I saw two examples of IV

RE: [PATCH] USB3/DWC3: Enable undefined length INCR burst type

> -Original Message- > From: Changming Huang [mailto:jerry.hu...@nxp.com] > Sent: Tuesday, December 13, 2016 5:06 PM > To: ba...@kernel.org; gre...@linuxfoundation.org > Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Jerry Huang > ; Rajesh Bhagat

RE: [PATCH] USB3/DWC3: Enable undefined length INCR burst type

> -Original Message- > From: Changming Huang [mailto:jerry.hu...@nxp.com] > Sent: Tuesday, December 13, 2016 5:06 PM > To: ba...@kernel.org; gre...@linuxfoundation.org > Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Jerry Huang > ; Rajesh Bhagat > Subject: [PATCH]

Re: Big I/O requests are split into small ones due to unaligned ext4 partition boundary?

On Thu, Dec 15, 2016 at 9:53 PM, Dexuan Cui wrote: >> From: Ming Lei [mailto:tom.leim...@gmail.com] >> Sent: Thursday, December 15, 2016 20:43 >> >> On Thu, Dec 15, 2016 at 7:47 PM, Dexuan Cui wrote: >> > Hi, when I run "mkfs.ext4 /dev/sdc2" in a Linux

Re: Big I/O requests are split into small ones due to unaligned ext4 partition boundary?

On Thu, Dec 15, 2016 at 9:53 PM, Dexuan Cui wrote: >> From: Ming Lei [mailto:tom.leim...@gmail.com] >> Sent: Thursday, December 15, 2016 20:43 >> >> On Thu, Dec 15, 2016 at 7:47 PM, Dexuan Cui wrote: >> > Hi, when I run "mkfs.ext4 /dev/sdc2" in a Linux virtual machine on Hyper-V, >> > where a

Re: [PATCH v3 2/2] drm/panel: simple: Add support BOE nv101wxmn51

Reviewed-by: Stéphane Marchesin On Tue, Dec 13, 2016 at 7:19 PM, Caesar Wang wrote: > 10.1WXGA is a color active matrix TFT LCD module using amorphous silicon > TFT's as an active switching devices. It can be supported by the > simple-panel driver. >

Re: [PATCH v3 2/2] drm/panel: simple: Add support BOE nv101wxmn51

Reviewed-by: Stéphane Marchesin On Tue, Dec 13, 2016 at 7:19 PM, Caesar Wang wrote: > 10.1WXGA is a color active matrix TFT LCD module using amorphous silicon > TFT's as an active switching devices. It can be supported by the > simple-panel driver. > > Read the panel default edid information:

Re: [alsa-devel] [PATCH v6 1/3] clk: x86: Add Atom PMC platform clocks

Hi Stephen, can you elaborate on the last comment? thanks, -Pierre On 12/13/2016 05:25 PM, Stephen Boyd wrote: + void __iomem *base, + const char **parent_names, + int

Re: [alsa-devel] [PATCH v6 1/3] clk: x86: Add Atom PMC platform clocks

Hi Stephen, can you elaborate on the last comment? thanks, -Pierre On 12/13/2016 05:25 PM, Stephen Boyd wrote: + void __iomem *base, + const char **parent_names, + int

Re: [PATCH] printk: Remove no longer used second struct cont

Joe Perches writes: > grep 2.5.4 was the last version that supported the -P option to > grep through for multiple lines. Does anybody know why it was dropped?

Re: [PATCH] printk: Remove no longer used second struct cont

Joe Perches writes: > grep 2.5.4 was the last version that supported the -P option to > grep through for multiple lines. Does anybody know why it was dropped?

[PATCH] vivid: Enable 4k resolution for webcam capture device

Add 3840x2160 as valid resolution for the webcam capture input and adjust the webcam intervals accordingly. Signed-off-by: Soren Brinkmann --- Hi, we'd like to use the vivid webcam capture device with a 4k resolution. This basically seems to do the trick, though, I'm

[PATCH] vivid: Enable 4k resolution for webcam capture device

Add 3840x2160 as valid resolution for the webcam capture input and adjust the webcam intervals accordingly. Signed-off-by: Soren Brinkmann --- Hi, we'd like to use the vivid webcam capture device with a 4k resolution. This basically seems to do the trick, though, I'm not sure if there is a

[ANNOUNCE]: SCST 3.2 released

Hi All, I'm glad to announce SCST 3.2 has just been released You can download it from http://scst.sourceforge.net/downloads.html SCST is alternative SCSI target stack for Linux. SCST allows creation of sophisticated storage devices, which can provide advanced functionality, like replication,

[ANNOUNCE]: SCST 3.2 released

Hi All, I'm glad to announce SCST 3.2 has just been released You can download it from http://scst.sourceforge.net/downloads.html SCST is alternative SCSI target stack for Linux. SCST allows creation of sophisticated storage devices, which can provide advanced functionality, like replication,

Re: Can't boot as Xen dom0 due to commit fe055896

On Fri, 16 Dec 2016, Borislav Petkov wrote: > What for? We don't want to run the microcode loader on xen at all. Or under KVM, or any other hypervisor, really. -- Henrique Holschuh

Re: Can't boot as Xen dom0 due to commit fe055896

On Fri, 16 Dec 2016, Borislav Petkov wrote: > What for? We don't want to run the microcode loader on xen at all. Or under KVM, or any other hypervisor, really. -- Henrique Holschuh

Re: Can't boot as Xen dom0 due to commit fe055896

On 12/15/2016 06:04 PM, Borislav Petkov wrote: On Thu, Dec 15, 2016 at 05:56:44PM -0500, Boris Ostrovsky wrote: With CONFIG_PARAVIRT (which I suspect you don't have on) cpuid() is a call via a pointer, you can see it, for example, if you disassemble load_ucode_amd_bsp(). And we don't have

Re: Can't boot as Xen dom0 due to commit fe055896

On 12/15/2016 06:04 PM, Borislav Petkov wrote: On Thu, Dec 15, 2016 at 05:56:44PM -0500, Boris Ostrovsky wrote: With CONFIG_PARAVIRT (which I suspect you don't have on) cpuid() is a call via a pointer, you can see it, for example, if you disassemble load_ucode_amd_bsp(). And we don't have

Re: [PATCH] usb: musb: debugfs: allow forcing host mode together with speed in testmode

On Wed, Dec 14, 2016 at 08:23:45PM +0100, Pali Rohár wrote: > Based on the musb ug, force_host bit is allowed to be set along with > force_hs or force_fs bit. > > It could help to implement forced host mode via testmode on Nokia N900. > > Signed-off-by: Pali Rohár > --- >

Re: [PATCH] usb: musb: debugfs: allow forcing host mode together with speed in testmode

On Wed, Dec 14, 2016 at 08:23:45PM +0100, Pali Rohár wrote: > Based on the musb ug, force_host bit is allowed to be set along with > force_hs or force_fs bit. > > It could help to implement forced host mode via testmode on Nokia N900. > > Signed-off-by: Pali Rohár > --- >

linux-next: Tree for Dec 16

Hi all, Please do not add any material for v4.11 to your linux-next included branches until after v4.10-rc1 has been released. Changes since 20161215: The vhost tree gained a conflict against the vfs tree. The akpm tree lost a patch that turned up elsewhere. Non-merge commits (relative

linux-next: Tree for Dec 16

Hi all, Please do not add any material for v4.11 to your linux-next included branches until after v4.10-rc1 has been released. Changes since 20161215: The vhost tree gained a conflict against the vfs tree. The akpm tree lost a patch that turned up elsewhere. Non-merge commits (relative

Re: [PATCH v5 1/4] siphash: add cryptographically secure PRF

Jean-Philippe Aumasson wrote: > If a halved version of SipHash can bring significant performance boost > (with 32b words instead of 64b words) with an acceptable security level > (64-bit enough?) then we may design such a version. It would be fairly significant, a 2x speed benefit on a lot of

Re: [PATCH v5 1/4] siphash: add cryptographically secure PRF

Jean-Philippe Aumasson wrote: > If a halved version of SipHash can bring significant performance boost > (with 32b words instead of 64b words) with an acceptable security level > (64-bit enough?) then we may design such a version. It would be fairly significant, a 2x speed benefit on a lot of

Re: [PATCH] watchdog: it87_wdt: add IT8620E ID

On 12/15/2016 02:52 PM, Maciej S. Szmigiero wrote: This adds IT8620E chip ID to it87_wdt driver. Such chip is often found on current Gigabyte motherboards, it is allegedly custom made for this manufacturer. Upon testing it looks like it has a 16-bit timer and cannot be reset via game port (only

Re: [PATCH] watchdog: it87_wdt: add IT8620E ID

On 12/15/2016 02:52 PM, Maciej S. Szmigiero wrote: This adds IT8620E chip ID to it87_wdt driver. Such chip is often found on current Gigabyte motherboards, it is allegedly custom made for this manufacturer. Upon testing it looks like it has a 16-bit timer and cannot be reset via game port (only

Re: [PATCH] hwmon: sch56xx: Remove unneeded linux/miscdevice.h include

On 12/15/2016 10:08 AM, Corentin Labbe wrote: drivers/hwmon/sch56xx-common.c does not contain any miscdevice so the inclusion of linux/miscdevice.h is uncessary. Signed-off-by: Corentin Labbe Reviewed-by: Guenter Roeck ---

Re: [PATCH] hwmon: sch56xx: Remove unneeded linux/miscdevice.h include

On 12/15/2016 10:08 AM, Corentin Labbe wrote: drivers/hwmon/sch56xx-common.c does not contain any miscdevice so the inclusion of linux/miscdevice.h is uncessary. Signed-off-by: Corentin Labbe Reviewed-by: Guenter Roeck --- drivers/hwmon/sch56xx-common.c | 1 - 1 file changed, 1

Re: [PATCH] watchdog: mpc8xxx: Remove unneeded linux/miscdevice.h include

On 12/15/2016 10:03 AM, Corentin Labbe wrote: watchdog/mpc8xxx_wdt.c does not use any miscdevice so this patch remove this unnecessary inclusion. Signed-off-by: Corentin Labbe Reviewed-by: Guenter Roeck --- drivers/watchdog/mpc8xxx_wdt.c | 1

Re: [PATCH] watchdog: mpc8xxx: Remove unneeded linux/miscdevice.h include

On 12/15/2016 10:03 AM, Corentin Labbe wrote: watchdog/mpc8xxx_wdt.c does not use any miscdevice so this patch remove this unnecessary inclusion. Signed-off-by: Corentin Labbe Reviewed-by: Guenter Roeck --- drivers/watchdog/mpc8xxx_wdt.c | 1 - 1 file changed, 1 deletion(-) diff --git

Re: [PATCH] watchdog: octeon: Remove unneeded linux/miscdevice.h include

On 12/15/2016 09:49 AM, Corentin Labbe wrote: watchdog/octeon-wdt-main.c does not use any miscdevice so this patch remove this unnecessary inclusion. Signed-off-by: Corentin Labbe Reviewed-by: Guenter Roeck ---

Re: [PATCH] watchdog: octeon: Remove unneeded linux/miscdevice.h include

On 12/15/2016 09:49 AM, Corentin Labbe wrote: watchdog/octeon-wdt-main.c does not use any miscdevice so this patch remove this unnecessary inclusion. Signed-off-by: Corentin Labbe Reviewed-by: Guenter Roeck --- drivers/watchdog/octeon-wdt-main.c | 1 - 1 file changed, 1 deletion(-) diff

[PATCH v6 3/5] random: use SipHash in place of MD5

This duplicates the current algorithm for get_random_int/long, but uses siphash instead. This comes with several benefits. It's certainly faster and more cryptographically secure than MD5. This patch also separates hashed fields into three values instead of one, in order to increase diffusion.

[PATCH v6 2/5] secure_seq: use SipHash in place of MD5

This gives a clear speed and security improvement. Siphash is both faster and is more solid crypto than the aging MD5. Rather than manually filling MD5 buffers, for IPv6, we simply create a layout by a simple anonymous struct, for which gcc generates rather efficient code. For IPv4, we pass the

[PATCH v6 3/5] random: use SipHash in place of MD5

This duplicates the current algorithm for get_random_int/long, but uses siphash instead. This comes with several benefits. It's certainly faster and more cryptographically secure than MD5. This patch also separates hashed fields into three values instead of one, in order to increase diffusion.

[PATCH v6 2/5] secure_seq: use SipHash in place of MD5

This gives a clear speed and security improvement. Siphash is both faster and is more solid crypto than the aging MD5. Rather than manually filling MD5 buffers, for IPv6, we simply create a layout by a simple anonymous struct, for which gcc generates rather efficient code. For IPv4, we pass the

[PATCH v6 5/5] syncookies: use SipHash in place of SHA1

SHA1 is slower and less secure than SipHash, and so replacing syncookie generation with SipHash makes natural sense. Some BSDs have been doing this for several years in fact. Signed-off-by: Jason A. Donenfeld --- net/ipv4/syncookies.c | 20

[PATCH v6 1/5] siphash: add cryptographically secure PRF

SipHash is a 64-bit keyed hash function that is actually a cryptographically secure PRF, like HMAC. Except SipHash is super fast, and is meant to be used as a hashtable keyed lookup function, or as a general PRF for short input use cases, such as sequence numbers or RNG chaining. For the first

[PATCH v6 5/5] syncookies: use SipHash in place of SHA1

SHA1 is slower and less secure than SipHash, and so replacing syncookie generation with SipHash makes natural sense. Some BSDs have been doing this for several years in fact. Signed-off-by: Jason A. Donenfeld --- net/ipv4/syncookies.c | 20 net/ipv6/syncookies.c | 37

[PATCH v6 1/5] siphash: add cryptographically secure PRF

SipHash is a 64-bit keyed hash function that is actually a cryptographically secure PRF, like HMAC. Except SipHash is super fast, and is meant to be used as a hashtable keyed lookup function, or as a general PRF for short input use cases, such as sequence numbers or RNG chaining. For the first

[PATCH v6 4/5] md5: remove from lib and only live in crypto

The md5_transform function is no longer used any where in the tree, except for the crypto api's actual implementation of md5, so we can drop the function from lib and put it as a static function of the crypto file, where it belongs. There should be no new users of md5_transform, anyway, since

[PATCH v6 4/5] md5: remove from lib and only live in crypto

The md5_transform function is no longer used any where in the tree, except for the crypto api's actual implementation of md5, so we can drop the function from lib and put it as a static function of the crypto file, where it belongs. There should be no new users of md5_transform, anyway, since

  1   2   3   4   5   6   7   8   9   10   >