Re: [PATCH v5] security/keys: rewrite all of big_key crypto

Hi Jason, On Sat, Sep 16, 2017 at 03:05:33PM +0200, Jason A. Donenfeld wrote: > - > - ret = big_key_gen_enckey(enckey); > - if (ret) > - goto err_enckey; > + ret = get_random_bytes_wait(enckey, ENC_KEY_SIZE); > + if

Re: printk: what is going on with additional newlines?

On (09/06/17 09:55), Petr Mladek wrote: [..] > > but I'm not super eager to have printk-safe based buffering. > > that's why I never posted a patch set. this approach has its > > limitations. > > Ah, I am happy to read this. From the previous mails, > I got the feeling that you were eager to go

include/linux/atomic.h:475:29: error: implicit declaration of function 'cmpxchg64'

Hi Rob, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e commit: 0ae349a0f33fb040a2bc228fdc6d60111455feab iommu/qcom: Add qcom_iommu date: 5 weeks ago config:

Re: Query regarding synchronize_sched_expedited and resched_cpu

On 09/17/2017 06:30 AM, Paul E. McKenney wrote: On Fri, Sep 15, 2017 at 04:44:38PM +0530, Neeraj Upadhyay wrote: Hi, We have one query regarding the behavior of RCU expedited grace period, for scenario where resched_cpu() in sync_sched_exp_handler() fails to acquire the rq lock and returns

[PATCH v4 4/5] input: Add MediaTek PMIC keys support

This patch add support to handle MediaTek PMIC MT6397/MT6323 key interrupts including pwrkey and homekey, also add setting for long press key shutdown behavior. Signed-off-by: Chen Zhong --- drivers/input/keyboard/Kconfig |9 +

[PATCH v4 5/5] mfd: mt6397: Add PMIC keys support to MT6397 driver

This patch adds compatible strings and interrupts for pmic keys which serves as child device of MFD. Acked-for-MFD-by: Lee Jones Signed-off-by: Chen Zhong --- drivers/mfd/mt6397-core.c | 22 +- 1 file changed, 21

[PATCH v4 1/5] mfd: mt6397: create irq mappings in mfd core driver

The core driver should create and manage irq mappings instead of leaf drivers. This patch change to pass irq domain to devm_mfd_add_devices() and it will create mapping for irq resources automatically. And remove irq mapping in rtc driver since this has been done in core driver. Acked-for-MFD-by:

[PATCH v4 2/5] dt-bindings: input: Add document bindings for mtk-pmic-keys

This patch adds the device tree binding documentation for the MediaTek pmic keys found on PMIC MT6397/MT6323. Signed-off-by: Chen Zhong --- .../devicetree/bindings/input/mtk-pmic-keys.txt| 41 1 file changed, 41 insertions(+) create mode

[PATCH v4 3/5] dt-bindings: mfd: Add bindings for the keys as subnode of PMIC

This patch adds documentation for device tree bindings for keys support as the subnode of MT6397/MT6323 PMIC. Acked-by: Rob Herring Acked-for-MFD-by: Lee Jones Signed-off-by: Chen Zhong ---

[PATCH 1/2] [media] tda18212: Delete an error message for a failed memory allocation in tda18212_probe()

From: Markus Elfring Date: Sun, 17 Sep 2017 09:33:58 +0200 * Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. * Add a jump target so that the function "kfree" will be always called

[PATCH 0/2] [media] TDA18212HN: Adjustments for two function implementations

From: Markus Elfring Date: Sun, 17 Sep 2017 10:03:45 +0200 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation Improve three size determinations

[PATCH 0/2] [media] Si2157: Adjustments for two function implementations

From: Markus Elfring Date: Sun, 17 Sep 2017 08:48:24 +0200 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation Improve a size determination in two functions

[linus:master] BUILD REGRESSION 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e Linux 4.14-rc1 arch/alpha/include/asm/mmu_context.h:160:24: error: invalid type argument of '->' (have 'int') arch/alpha/include/asm/mmu_context.h:160:2: error: implicit

Re: [lkp-robot] [sched/fair] 6d46bd3d97: netperf.Throughput_tps -11.3% regression

Hi Rik, On Thu, Sep 14, 2017 at 8:56 AM, Rik van Riel wrote: > On Sun, 2017-09-10 at 23:32 -0700, Joel Fernandes wrote: >> >> To make the load check more meaningful, I am thinking if using >> wake_affine()'s balance check is a better thing to do than the >> 'nr_running < 2'

[PATCH 1/2] [media] si2157: Delete an error message for a failed memory allocation in si2157_probe()

From: Markus Elfring Date: Sun, 17 Sep 2017 08:20:04 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 2/2] [media] si2157: Improve a size determination in two functions

From: Markus Elfring Date: Sun, 17 Sep 2017 08:32:17 +0200 Replace the specification of data structures by variable references as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

Re: [PATCH v2] ARM: dts: exynos: fix incomplete Odroid-XU3/4 thermal-zones definition

On Fri, Sep 08, 2017 at 06:40:15PM +0200, Krzysztof Kozlowski wrote: > On Thu, Sep 07, 2017 at 06:10:00PM +0200, Bartlomiej Zolnierkiewicz wrote: > > From: Willy Wolff > > > > Odroid XU3/4 boards have thermal sensors per 4 pairs of A7+A15 > > cores but currently there

Re: [PATCH v4 3/3] ARM: dts: exynos: Remove the display-timing and delay from rinato dts

On Tue, Aug 29, 2017 at 07:58:52AM +0200, Krzysztof Kozlowski wrote: > On Tue, Aug 29, 2017 at 4:52 AM, Hoegeun Kwon > wrote: > > Hi Krzysztof, > > > > The driver has been merged into exynos-drm-misc. > > Could you please check this patch(3/3). > > Hi, OK, no problems

Re: [PATCH v7 0/3] nvmem: upstream snvs_lpgpr driver

On 26/07/2017 12:01, Srinivas Kandagatla wrote: > > On 18/07/17 05:52, Oleksij Rempel wrote: >> Hallo all, >> >> Here Gentle Ping to the Old King ;) >> >> DT is already ACKed. > > Thanks for patience, As this is a new driver it will be queued for 4.14 just > before 4.13-rc5 is released. > >

[PATCH v4 0/5] Add MediaTek PMIC keys support

Changes since v3: - make the naming to be consistent as mtk_pmic or MTK_PMIC - add suspend/resume functions to enable/disable irq - change binding properties to define wakeup sources Changes since v2: - use standard properties for keycodes and debounce time - change to use platform_get_irq in

Re: [PATCH 2/4] arm: dts: exynos: add exynos5420 cpu capacity-dmips-mhz information

On Wed, Aug 30, 2017 at 03:41:18PM +0100, Dietmar Eggemann wrote: > The following 'capacity-dmips-mhz' dt property values are used: > > Cortex-A15: 1024, Cortex-A7: 539 > > They have been derived from the cpu_efficiency values: > > Cortex-A15: 3891, Cortex-A7: 2048 > > by scaling them so that

Re: [GIT PULL] Security subsystem updates for 4.14

On Sat, 2017-09-09 at 05:57 +1000, James Morris wrote: > On Fri, 8 Sep 2017, Linus Torvalds wrote: > > > Now the whole security pull will be ignored because of this thing. I > > refuse to pull garbage where I notice major fundamental problems in > > code that has obviously never ever been tested.

Re: [PATCH 3/4] arm: dts: exynos: add exynos5422 cpu capacity-dmips-mhz information

On Wed, Aug 30, 2017 at 03:41:19PM +0100, Dietmar Eggemann wrote: > The following 'capacity-dmips-mhz' dt property values are used: > > Cortex-A15: 1024, Cortex-A7: 539 > > They have been derived form the cpu_efficiency values: > > Cortex-A15: 3891, Cortex-A7: 2048 > > by scaling them so that

[PATCH 2/2] [media] airspy: Improve a size determination in airspy_probe()

From: Markus Elfring Date: Sun, 17 Sep 2017 11:03:21 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[GIT pull] core fixes for 4.14

Linus, please pull the latest core-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-urgent-for-linus This update contains: - A fix for a user space regression in /proc/$PID/stat - A couple of objtool fixes: - Plug a memory leak -

[PATCH] [media] au0828: Delete an error message for a failed memory allocation in au0828_usb_probe()

From: Markus Elfring Date: Sun, 17 Sep 2017 11:40:31 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 1/2] nvmem: dt: document SNVS LPGPR binding

From: Oleksij Rempel Documentation bindings for the Low Power General Purpose Register available on i.MX6 SoCs in the Secure Non-Volatile Storage. Signed-off-by: Oleksij Rempel Acked-by: Rob Herring Signed-off-by: Srinivas

[PATCH 2/2] nvmem: add snvs_lpgpr driver

From: Oleksij Rempel This is a driver for Low Power General Purpose Register (LPGPR) available on i.MX6 SoCs in Secure Non-Volatile Storage (SNVS) of this chip. It is a 32-bit read/write register located in the low power domain. Since LPGPR is located in the

[PATCH 0/2] nvmem: set3 patches for v4.14

From: Srinivas Kandagatla Hi Greg, snvs nvmem provider driver was missed in first and second set of nvmem patches, this driver has been acked and reviewed. Could you please pick this up for 4.14. Thanks, srini Oleksij Rempel (2): Oleksij Rempel (2): nvmem:

Re: [PATCH v3] Make initramfs honor CONFIG_DEVTMPFS_MOUNT

On Sat, 16 Sep 2017, Rob Landley wrote: > So, I added a workaround with a printk in hopes of embarassing them into > someday fixing it. Oh, it will be fixed in Debian alright. I am just waiting the issue to settle a bit to file the bug reports, or maybe even send in the Debian patches myself

Re: [GIT PULL] overlayfs update for 4.14

Linus Torvalds: > On Wed, Sep 13, 2017 at 11:46 PM, Miklos Szeredi wrote: > > > > d_real() is currently is *the* overlayfs-op: > > I know. And it's ugly as #%^! hell. > > We don't want to make it uglier. > > And honestly, if you think that "it's only for overlayfs, so I can do

[PATCH] bitfield.h: include instead of

Since commit bc6245e5efd7 ("bug: split BUILD_BUG stuff out into "), #include is better to pull minumam headers needed for BUILG_BUG() family. Signed-off-by: Masahiro Yamada --- include/linux/bitfield.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH 2/2] [media] tda18212: Improve three size determinations

From: Markus Elfring Date: Sun, 17 Sep 2017 09:42:17 +0200 Replace the specification of data structures by variable references as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 1/2] [media] airspy: Delete an error message for a failed memory allocation in airspy_probe()

From: Markus Elfring Date: Sun, 17 Sep 2017 11:00:09 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[GIT pull] irq fix for 4.14

Linus, please pull the latest irq-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-urgent-for-linus Fix for an off by one error in a cpumask result comparison. Thanks, tglx --> Thomas Gleixner (1): genirq: Fix

[PATCH] dlm: Reuse existing error handling path

The error handling path at label 'accept_err' already performs these 'sock_release()' and 'mutex_unlock()' calls. The order is reversed, but it is not important. So avoid code duplication and 'goto accept_err'. While at it, add some missing spaces around a '='. Signed-off-by: Christophe JAILLET

[PATCH] mtd: spi-nor: Check for spi_nor_hwcaps_read2cmd() return value

The function can return a negativ value in case of errors, don't use it blindly as array index. Detected by CoverityScan CID#1418067 ("Memory - illegal accesses") Fixes: f384b352cbf0 ("mtd: spi-nor: parse Serial Flash Discoverable Parameters (SFDP) tables") Signed-off-by: Richard Weinberger

Re: [PATCH v7 0/3] nvmem: upstream snvs_lpgpr driver

On 17/09/17 08:35, Guy Shapiro wrote: On 26/07/2017 12:01, Srinivas Kandagatla wrote: On 18/07/17 05:52, Oleksij Rempel wrote: Hallo all, Here Gentle Ping to the Old King ;) DT is already ACKed. Thanks for patience, As this is a new driver it will be queued for 4.14 just before

Re: [PATCH v5] security/keys: rewrite all of big_key crypto

On Sun, Sep 17, 2017 at 8:04 AM, Eric Biggers wrote: > This should jump to 'err_enckey', otherwise it will leak 'enckey'. Yikes, good catch, thanks! > > Otherwise the changes all look good; after fixing the above, feel free to add > my > Reviewed-by. Ack. > Yes, AES-GCM

[PATCH] IB/mlx5: fix debugfs cleanup

If delay_drop_debugfs_init() fails in any of the operations to create debugfs, it is calling delay_drop_debugfs_cleanup() as part of its cleanup. But delay_drop_debugfs_cleanup() checks for 'dbg' and since we have not yet pointed 'dbg' to the debugfs we need to cleanup the cleanup fails and we are

Re: [Part1 PATCH v4 07/17] x86/efi: Access EFI data as encrypted when SEV is active

On Sat, Sep 16, 2017 at 07:34:08AM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > EFI data is encrypted when the kernel is run under SEV. Update the > page table references to be sure the EFI memory areas are accessed > encrypted. > > Cc: Thomas Gleixner

Re: [Part1 PATCH v4 05/17] x86/mm: Use encrypted access of boot related data with SEV

On Sat, Sep 16, 2017 at 07:34:06AM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > When Secure Encrypted Virtualization (SEV) is active, boot data (such as > EFI related data, setup data) is encrypted and needs to be accessed as > such when mapped. Update the

Re: [Part1 PATCH v4 06/17] x86/mm: Include SEV for encryption memory attribute changes

On Sat, Sep 16, 2017 at 07:34:07AM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > The current code checks only for sme_active() when determining whether > to perform the encryption attribute change. Include sev_active() in this > check so that memory attribute

Re: [Part1 PATCH v4 02/17] x86/mm: Add Secure Encrypted Virtualization (SEV) support

On Sat, Sep 16, 2017 at 07:34:03AM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > Provide support for Secure Encrypted Virtualization (SEV). This initial > support defines a flag that is used by the kernel to determine if it is > running with SEV active. > > Cc:

Re: [Part1 PATCH v4 03/17] x86/mm: Don't attempt to encrypt initrd under SEV

On Sat, Sep 16, 2017 at 07:34:04AM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > When SEV is active the initrd/initramfs will already have already been > placed in memory encrypted so do not try to encrypt it. > > Cc: Thomas Gleixner > Cc:

[PATCH] MIPS: MSP71xx: fix build failure

The build of msp71xx_defconfig was failing with the error: arch/mips/pmcs-msp71xx/msp_smp.c: In function 'msp_vsmp_int_init': arch/mips/pmcs-msp71xx/msp_smp.c:72:2: error: implicit declaration of function 'set_vi_handler'; did you mean 'irq_set_handler'?

Re: [Part1 PATCH v4 12/17] x86/boot: Add early boot support when running with SEV active

On Sat, Sep 16, 2017 at 07:34:13AM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > Early in the boot process, add checks to determine if the kernel is > running with Secure Encrypted Virtualization (SEV) active. > > Checking for SEV requires checking that the

[PATCH] radix-tree: remove unneeded #include

This include was added by commit 187f1882b5b0 ("BUG: headers with BUG/BUG_ON etc. need linux/bug.h") because BUG_ON() was used in this header at that time. Some time later, commit 6d75f366b924 ("lib: radix-tree: check accounting of existing slot replacement users") removed the use of BUG_ON()

[PATCH] mm: introduce sanity check on dirty ratio sysctl value

we can find the logic in domain_dirty_limits() that when dirty bg_thresh is bigger than dirty thresh, bg_thresh will be set as thresh * 1 / 2. if (bg_thresh >= thresh) bg_thresh = thresh / 2; But actually we can set dirty_background_raio bigger than dirty_ratio

Re: [PATCH v7 0/3] nvmem: upstream snvs_lpgpr driver

Hi Guy, > Guy Shapiro hat am 17. September 2017 um 09:35 > geschrieben: > > > On 26/07/2017 12:01, Srinivas Kandagatla wrote: > > > > On 18/07/17 05:52, Oleksij Rempel wrote: > >> Hallo all, > >> > >> Here Gentle Ping to the Old King ;) > >> > >> DT is already

Re: [PATCH 3/3 v11] printk: Add monotonic, boottime, and realtime timestamps

On (09/15/17 07:29), Mark Salyzyn wrote: > On 09/15/2017 06:28 AM, Petr Mladek wrote: > > I am still slightly nervous that external tools would need updating. > > Also they might have troubles to interpret the time stamps especially > > when the source is changed at runtime via > >

[PATCH 2/4] [media] cpia2: Adjust two function calls together with a variable assignment

From: Markus Elfring Date: Sun, 17 Sep 2017 12:56:50 +0200 The script "checkpatch.pl" pointed information out like the following. ERROR: do not use assignment in if condition Thus fix the affected source code places. Signed-off-by: Markus Elfring

Re: [PATCH 2/2] arm: dts: stm32: remove useless clocksource nodes

2017-09-15 23:03 GMT+02:00 Daniel Lezcano : > On Thu, Sep 14, 2017 at 09:56:52AM +0200, Benjamin Gaignard wrote: >> 16 bits timers aren't accurate enough to be used as >> clocksource, remove them from stm32f4 and stm32f7 devicetree. > > Do you really want to remove the

Re: [Part1 PATCH v4 04/17] x86/realmode: Don't decrypt trampoline area under SEV

On Sat, Sep 16, 2017 at 07:34:05AM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > When SEV is active the trampoline area will need to be in encrypted > memory so only mark the area decrypted if SME is active. > > Cc: Thomas Gleixner > Cc: Ingo

Re: [Part1 PATCH v4 10/17] x86/mm, resource: Use PAGE_KERNEL protection for ioremap of memory pages

On Sat, Sep 16, 2017 at 07:34:11AM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > In order for memory pages to be properly mapped when SEV is active, we > need to use the PAGE_KERNEL protection attribute as the base protection. > This will insure that memory

Re: [Part1 PATCH v4 11/17] x86/mm: DMA support for SEV memory encryption

On Sat, Sep 16, 2017 at 07:34:12AM -0500, Brijesh Singh wrote: Add a verb to patch subject: Subject: x86/mm: Add DMA support for ... > From: Tom Lendacky > > DMA access to encrypted memory cannot be performed when SEV is active. > In order for DMA to properly work

Re: [Part1 PATCH v4 08/17] resource: Consolidate resource walking code

On Sat, Sep 16, 2017 at 07:34:09AM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > The walk_iomem_res_desc(), walk_system_ram_res() and walk_system_ram_range() > functions each have much of the same code. Create a new function that > consolidates the common code

Dear Talented

Dear Talented, I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a Film Corporation Located in the United State, is Soliciting for the Right to use Your Photo/Face and Personality as One of the Semi -Major Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story

Re: [PATCH V2] tipc: Use bsearch library function

> Am 16.09.2017 um 15:20 schrieb Jon Maloy . >> >> What part of "very time critical" have you verified and benchmarked as >> inconsequential? >> >> Please post your results. > > I agree with Joe here. This change does not simplify anything, it does not > reduce the

[PATCH] checkpatch: do not check missing blank line before builtin_*_driver

checkpatch.pl does not check missing blank line before module_*_driver. I want it to behave likewise for builtin_*_driver. Signed-off-by: Masahiro Yamada --- scripts/checkpatch.pl | 1 + 1 file changed, 1 insertion(+) diff --git a/scripts/checkpatch.pl

[PATCH 0/2] [media] AirSpy: Adjustments for airspy_probe()

From: Markus Elfring Date: Sun, 17 Sep 2017 11:11:02 +0200 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation Improve a size determination

[PATCH] hamradio: baycom: use new parport device model

Modify baycom driver to use the new parallel port device model. Signed-off-by: Sudip Mukherjee --- Not tested on real hardware, only tested on qemu and verified that the device is binding to the driver properly in epp_open but then unbinding as the device was not

[PATCH] rpmsg: glink: fix memory leak

We missed freeing intent and intent->data on error conditions. Signed-off-by: Sudip Mukherjee --- drivers/rpmsg/qcom_glink_native.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/drivers/rpmsg/qcom_glink_native.c

Re: [PATCH] dma-coherent: fix rmem_dma_device_init regression

On 9/15/2017 11:08 AM, Arnd Bergmann wrote: > My recent bug fix introduced another bug, which caused rmem_dma_device_init > to always fail, as rmem->priv is never set to anything. > > This restores the previous behavior, calling dma_init_coherent_memory() > whenever ->priv is NULL. > > Fixes:

[PATCH 0/4] [media] CPia2: Fine-tuning for four function implementations

From: Markus Elfring Date: Sun, 17 Sep 2017 15:25:35 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (4): Use common error handling code in cpia2_usb_probe() Adjust two function calls together with a

[PATCH 1/4] [media] cpia2: Use common error handling code in cpia2_usb_probe()

From: Markus Elfring Date: Sun, 17 Sep 2017 12:40:14 +0200 Add a jump target so that a bit of exception handling can be better reused at the end of this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring

[PATCH] mtd: spi-nor: Kill check with no effect

header.major is of type u8 and cannot be negative. Detected by CoverityScan CID#1417858 ("Integer handling issues") Fixes: f384b352cbf0 ("mtd: spi-nor: parse Serial Flash Discoverable Parameters (SFDP) tables") Signed-off-by: Richard Weinberger --- Cyrille, I'm not sure what

[RFC PATCH] dmaengine: sh: Correct src_addr_widths/dst_addr_widths bitmask setting

Obviously, the current value for the burst widths are wrong, and if this value is retrieved from some other subsystem using dma_get_slave_caps, it will wrongly assume burst width of e.g. 3 bytes are supported. Each bit in the bitmask corresponds to a supported width, but it uses an encoding of

[RFC RESEND 1/3] clk: hisilicon: add CRG driver Hi3521A SoC

Add CRG driver for Hi3521A SoC. CRG (Clock and Reset Generator) module generates clock and reset signals used by other module blocks on SoC. Signed-off-by: Marty E. Plummer --- drivers/clk/hisilicon/Kconfig | 7 + drivers/clk/hisilicon/Makefile|

[RFC RESEND 3/3] arm: dts: add Hi3521A dts

Add hi3521a.dtsi and hi3521a-rs-dm290e.dts for RaySharp CCTV systems, marketed under the name Samsung SDR-B74301N Signed-off-by: Marty E. Plummer --- arch/arm/boot/dts/Makefile | 2 + arch/arm/boot/dts/hi3521a-rs-dm290e.dts | 52 ++

[RFC RESEND 2/3] arm: hisi: enable Hi3521A SoC

Enable Hisilicon Hi3521A/Hi3520DCV300 SoC. This SoC series includes hardware mutlimedia codec cores, commonly used in consumer cctv/dvr security systems and ipcameras. The arm core is a Cortex A7. Signed-off-by: Marty E. Plummer --- arch/arm/mach-hisi/Kconfig | 6 ++

[RFC RESEND 0/3] Add support for Hisilicon Hi3521A SoC

Greetings, I'd like the community's feedback on the following patchset. I've attempted to split my changes up in what I believe to be a sensible setup. The device I'm working against is the 'SamsungSV SDR-B74301' HD CCTV surveillance system, which uses a Hisilicon Hi3521A arm SoC as its basis.

Re: printk: what is going on with additional newlines?

On (09/17/17 15:26), Sergey Senozhatsky wrote: [..] > > Anyway, it seems that we will need to update all the tools > > for the different time stamps, see > > https://lkml.kernel.org/r/1504613201-23868-1-git-send-email-pra...@redhat.com > > Then we will be more clever how painful it is. may be we

[GIT pull] x86 fix for 4.14

Linus, please pull the latest x86-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus A single fix addressing the missing CP8 feature bit in CPUID for a range of AMD ZEN models/mask revisions. Thanks, tglx

[PATCH] tracing: fix trace_pipe behavior for instance traces

When reading data from trace_pipe, tracing_wait_pipe() performs a check to see if tracing has been turned off after some data was read. Currently, this check always looks at global trace state, but it should be checking the trace instance where trace_pipe is located at. Because of this bug, cat

[PATCH v6] security/keys: rewrite all of big_key crypto

This started out as just replacing the use of crypto/rng with get_random_bytes_wait, so that we wouldn't use bad randomness at boot time. But, upon looking further, it appears that there were even deeper underlying cryptographic problems, and that this seems to have been committed with very little

Re: [PATCH] drm/amdkfd: check for null dev to avoid a null pointer dereference

On Fri, Sep 8, 2017 at 5:13 PM, Colin King wrote: > From: Colin Ian King > > The call to kfd_device_by_id can potentially return null, so check that > dev is null and return with -EINVAL to avoid a null pointer dereference. > > Detected by

[PATCH] rtc: sun6i: fix memory leak

If 'clk_data' is not allocated we returned but we failed to free 'rtc'. Signed-off-by: Sudip Mukherjee --- drivers/rtc/rtc-sun6i.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/rtc/rtc-sun6i.c b/drivers/rtc/rtc-sun6i.c index

Re: 319554f284dd ("inet: don't use sk_v6_rcv_saddr directly") causes bind port regression

On 09/15/2017 01:51 PM, Josef Bacik wrote: > Finally got access to a box to run this down myself. This patch on top of > the other patches fixes the problem for me, could you verify it works for > you? Thanks, > Yup I can confirm that patch fixes things when applied on top of the previous 3

[PATCH 3/4] [media] cpia2: Delete unnecessary null pointer checks in free_sbufs()

From: Markus Elfring Date: Sun, 17 Sep 2017 13:23:47 +0200 The script "checkpatch.pl" pointed information out like the following. WARNING: kfree(NULL) is safe and this check is probably not required Thus fix the affected source code place. Signed-off-by: Markus

[PATCH 4/4] [media] cpia2: Delete an unnecessary return statement in process_frame()

From: Markus Elfring Date: Sun, 17 Sep 2017 13:32:45 +0200 The script "checkpatch.pl" pointed information out like the following. WARNING: void function return statements are not generally useful Thus remove such a statement in the affected function.

[PATCH] dmaengine: edma: Reject slave configs using a buswidth of 8 and larger

The driver would happily accept buswidth of 16/32/64 bytes and program garbage to its registers. Signed-off-by: Stefan Brüns --- drivers/dma/edma.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/dma/edma.c b/drivers/dma/edma.c index

[PATCH] printk: simplify no_printk()

Commit 069f0cd00df0 ("printk: Make the printk*once() variants return a value") surrounded the macro implementation with ({ ... }). Now, the inner do { ... } while (0); is redundant. Signed-off-by: Masahiro Yamada --- include/linux/printk.h | 6 ++ 1 file

Re: [Part1 PATCH v4 13/17] x86/io: Unroll string I/O when SEV is active

On Sat, Sep 16, 2017 at 07:34:14AM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > Secure Encrypted Virtualization (SEV) does not support string I/O, so > unroll the string I/O operation into a loop operating on one element at > a time. > > Cc: Thomas Gleixner

Re: [PATCH 3/3] ima: use fs method to read integrity data (updated patch description)

On Sat, Sep 16, 2017 at 11:20:47AM -0700, Linus Torvalds wrote: > Sure, generic_file_write_iter() does take that lock exclusively, but > not everybody uses generic_file_write_iter() at all for writing. > > For example, xfs still uses that i_rwsem, but for block-aligned writes > it will only get

Dear Talented

Dear Talented, I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a Film Corporation Located in the United State, is Soliciting for the Right to use Your Photo/Face and Personality as One of the Semi -Major Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story

Re: [linus:master] BUILD REGRESSION 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e

Fengguang, it looks like the kernel build robot _only_ tests the actual rc kernels, and doesn't bisect down where the error started. Any change that when it notices an error, it would bisect it, like it does for linux-next? Linus On Sat, Sep 16, 2017 at 11:02 PM, kbuild test

[PATCH 0/4] More PCID fixes

This fixes a 32-bit boot warning, a 32-bit boot oddity that seems unsymtomatic right now, and a potential userspace corruption issue across EFI calls if PCID is enabled. With this series applied, the only remaining issue I'm aware of is the paging-structure cache laziness problem. I've tested

Re: [PATCH 3/3] ima: use fs method to read integrity data (updated patch description)

On Sun, Sep 17, 2017 at 9:15 AM, Mimi Zohar wrote: > > Unless I'm missing something, that would only be possible with an IMA > policy rule that permits direct IO (eg. permit_directio). Otherwise > the direct IO is denied. Note that the "XFS and directio" was only an

Re: [PATCH 3/3] ima: use fs method to read integrity data (updated patch description)

On Sun, Sep 17, 2017 at 09:34:01AM -0700, Linus Torvalds wrote: > Now, I suspect most (all?) do, but that's a historical artifact rather > than "design". In particular, the VFS layer used to do the locking for > the filesystems, to guarantee the POSIX requirements (POSIX requires > that writes be

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

On 09/16/2017 12:30 AM, Dmitry Torokhov wrote: > On Fri, Sep 15, 2017 at 2:55 PM, Jacek Anaszewski > wrote: >> On 09/15/2017 08:34 PM, Dmitry Torokhov wrote: >>> On Thu, Sep 14, 2017 at 1:58 PM, Pavel Machek wrote: On Thu 2017-09-14 21:31:31, Jacek

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

Hi, On 09/16/2017 03:58 AM, Pavel Machek wrote: > Hi! > >> These patch series add the LED_BRIGHTNESS_FAST flag support for >> ledtrig-transient to use hrtimer so that platforms with high-resolution >> timer >> support can have better accuracy in the trigger duration timing. The

Re: Build regressions/improvements in v4.14-rc1

On Sun, Sep 17, 2017 at 6:54 PM, Geert Uytterhoeven wrote: > On Sun, Sep 17, 2017 at 4:36 PM, Geert Uytterhoeven > wrote: >> Below is the list of build error/warning regressions/improvements in >> v4.14-rc1[1] compared to v4.13[2]. >> >> Summarized: >>

Re: Build regressions/improvements in v4.14-rc1

On Sun, Sep 17, 2017 at 4:36 PM, Geert Uytterhoeven wrote: > Below is the list of build error/warning regressions/improvements in > v4.14-rc1[1] compared to v4.13[2]. > > Summarized: > - build errors: +7/-0 > [1] >

[PATCH] alpha: fix build failures

The build of alpha allmodconfig is giving error: arch/alpha/include/asm/mmu_context.h: In function 'ev5_switch_mm': arch/alpha/include/asm/mmu_context.h:160:2: error: implicit declaration of function 'task_thread_info'; did you mean 'init_thread_info'?

Re: [PATCH v4 2/3] mm: introduce MAP_VALIDATE a mechanism for adding new mmap flags

On Sat, Sep 16, 2017 at 08:44:14PM -0700, Dan Williams wrote: > So it wasn't all that easy, and Linus declined to take it. I think we > should add a new ->mmap_validate() file operation and save the > tree-wide cleanup until later. Note that we already have a mmap_capabilities callout for nommu,

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

Hi! > >> Do you think such an improvement could be harmful in some way, > >> even if it was made optional? > > > > Of course, we can make LED timing accurate down to microseconds. It will > > mean increased overhead -- for "improvement" human can not perceive. > > > > If someone has problems

[PATCH] tools/kvm_stat: Add Python 3 support to kvm_stat

Make kvm_stat support Python 3 by changing the use of "print" to a function rather than a statement and switching from "iteritems" (removed in Python 3) to "items". With this change, kvm_stat is usable with Python 2.6 and greater. Signed-off-by: Jeremy Cline ---

[tip:core/urgent] arm/syscalls: Optimize address limit check

Commit-ID: e33f8d32677fa4f4f8996ef46748f86aac81ccff Gitweb: http://git.kernel.org/tip/e33f8d32677fa4f4f8996ef46748f86aac81ccff Author: Thomas Garnier AuthorDate: Thu, 7 Sep 2017 08:30:46 -0700 Committer: Thomas Gleixner CommitDate: Sun, 17 Sep

[tip:core/urgent] arm64/syscalls: Move address limit check in loop

Commit-ID: a2048e34d4655c06d31400646ae495bbfeb16b27 Gitweb: http://git.kernel.org/tip/a2048e34d4655c06d31400646ae495bbfeb16b27 Author: Thomas Garnier AuthorDate: Thu, 7 Sep 2017 08:30:47 -0700 Committer: Thomas Gleixner CommitDate: Sun, 17 Sep

  1   2   3   4   5   6   >