[GIT PULL] Immutable branch between MFD, Input and RTC due for the v3.14 merge window

Enjoy! The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877: Linux v4.13-rc1 (2017-07-15 15:22:10 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git ib-mfd-input-rtc-v4.14 for you to fetch changes up to

[PATCH v2 0/3] STM32 CRYP crypto driver

This set of patches adds a new crypto driver for STMicroelectronics stm32 HW. This drivers uses the crypto API and provides with HW-enabled AEAD and block cipher algorithms. It makes use of the crypto engine which is upgraded in order to support AEAD requests. This driver was successfully tested

Re: [PATCH V3 2/2] It makes the code clearer and less error prone.

On Monday, August 14, 2017 7:33:41 PM CEST Steven Rostedt wrote: > On Thu, 3 Aug 2017 00:15:58 +0200 > Federico Vaga wrote: > > Why did you change the subject? The previous patch had a much better > one: "trace-cmd: Use asprintf when possible" > > Or was it the tool

RE: [PATCH 2/3] crypto: engine - find request type with cra_type

Hi Corentin, Since I have just sent a patch to add the support of "aead_request" to crypto engine, I am wondering if your proposed change (checking cra_type instead of crypto_tfm_alg_type) and mine are compatible. It looks like they are (assuming we export crypto_aead_type): can you confirm? BR

Re: linux-next: manual merge of the akpm-current tree with the tip tree

Peter Zijlstra wrote: > On Mon, Aug 14, 2017 at 05:07:19AM +, Nadav Amit wrote: So I'm not entirely clear about this yet. How about: CPU0CPU1 tlb_gather_mmu()

RE: [PATCH V2] kernel/watchdog: fix spurious hard lockups

On Tue, 15 Aug 2017, Liang, Kan wrote: > This patch which speed up the hrtimer (https://lkml.org/lkml/2017/6/26/685) > is decent to fix the spurious hard lockups. > Tested-by: Kan Liang > > Please consider to merge it into both mainline and stable tree. Well, it 'fixes' the

[PATCH] btrfs: remove redundant check on ret being non-zero

From: Colin Ian King The error return variable ret is initialized to zero and then is checked to see if it is non-zero in the if-block that follows it. It is therefore impossible for ret to be non-zero after the if-block hence the check is redundant and can be removed.

Re: early x86 unseeded randomness

On Tue, Aug 15, 2017 at 09:42:54AM +0200, Ingo Molnar wrote: > > * Willy Tarreau wrote: > > > Nowadays we could use similar methods using RDTSC providing more accurate > > counting. This doesn't provide a lot of entropy of course, given that a > > 2 GHz machine will at most count

Re: [PATCH v5 0/6] drivers/i2c: Add FSI-attached I2C master algorithm

On Tue, Aug 15, 2017 at 4:06 PM, Peter Rosin wrote: > On 2017-07-26 19:13, Eddie James wrote: >> From: "Edward A. James" >> >> This series adds an algorithm for an I2C master physically located on an FSI >> slave device. The I2C master has multiple ports,

Re: [PATCH v5 04/19] crypto: marvell/cesa: remove redundant backlog checks on EBUSY

Le Mon, 14 Aug 2017 18:21:14 +0300, Gilad Ben-Yossef a écrit : > Now that -EBUSY return code only indicates backlog queueing > we can safely remove the now redundant check for the > CRYPTO_TFM_REQ_MAY_BACKLOG flag when -EBUSY is returned. > > Signed-off-by: Gilad Ben-Yossef

Re: [PATCH V1] mfd: da9061: fix to remove BBAT_CONT register from chip model

On Mon, 14 Aug 2017, Steve Twiss wrote: > On 06 June 2017 08:16, Lee Jones wrote: > > > drivers/mfd/da9062-core.c | 6 -- > > > 1 file changed, 6 deletions(-) > > > > Applied, thanks. > > $ git describe > v4.13-rc5 > > Looking at linux-mainline today, I noticed a commit that seems to be

[PATCH 3/3] ALSA: firewire-motu: constify snd_rawmidi_ops structures

These snd_rawmidi_ops structures are only passed as the third argument of snd_rawmidi_set_ops. This argument is const, so the snd_rawmidi_ops structures can be const too. Done with the help of Coccinelle. Signed-off-by: Julia Lawall --- sound/firewire/motu/motu-midi.c |

[PATCH 1/3] usb: gadget: f_midi: constify snd_rawmidi_ops structures

These snd_rawmidi_ops structures are only passed as the third argument of snd_rawmidi_set_ops. This argument is const, so the snd_rawmidi_ops structures can be const too. Done with the help of Coccinelle. Signed-off-by: Julia Lawall ---

Re: Re: [PATCH 2/2] mm, oom: fix potential data corruption when oom_reaper races with writer

On Tue 15-08-17 07:51:02, Tetsuo Handa wrote: > Michal Hocko wrote: [...] > > Were you able to reproduce with other filesystems? > > Yes, I can reproduce this problem using both xfs and ext4 on > 4.11.11-200.fc25.x86_64 > on Oracle VM VirtualBox on Windows. Just a quick question.

Re: [PATCH 3/3] ALSA: firewire-motu: constify snd_rawmidi_ops structures

Hi, On Aug 15 2017 17:09, Julia Lawall wrote: These snd_rawmidi_ops structures are only passed as the third argument of snd_rawmidi_set_ops. This argument is const, so the snd_rawmidi_ops structures can be const too. Done with the help of Coccinelle. Signed-off-by: Julia Lawall

Re: [PATCH 3/3] ALSA: firewire-motu: constify snd_rawmidi_ops structures

On Tue, 15 Aug 2017 10:09:54 +0200, Julia Lawall wrote: > > These snd_rawmidi_ops structures are only passed as the third > argument of snd_rawmidi_set_ops. This argument is const, so the > snd_rawmidi_ops structures can be const too. > > Done with the help of Coccinelle. > > Signed-off-by:

Re: [PATCH 2/3] HID: prodikeys: constify snd_rawmidi_ops structures

On Tue, 15 Aug 2017, Julia Lawall wrote: > This snd_rawmidi_ops structure is only passed as the third > argument of snd_rawmidi_set_ops. This argument is const, so the > snd_rawmidi_ops structure can be const too. > > Done with the help of Coccinelle. > > Signed-off-by: Julia Lawall

[PATCH v3 0/9] Add PMIC support to MediaTek MT7622 SoC

From: Sean Wang Changes since v2: - for patch 1/2, enhance the document as the suggestions from v2. - for patch 3, constify the table with struct regulator_ops, also fix that regulator doesn't have modesetting facilities it just shouldn't have the ops and finally fix

Re: [PATCH] irq_work: improve the flag definitions

2017-08-14 13:56 GMT+02:00 Bartosz Golaszewski : > IRQ_WORK_FLAGS is defined simply to 3UL. This is confusing as it > says nothing about its purpose. Define IRQ_WORK_FLAGS as a bitwise > OR of IRQ_WORK_PENDING and IRQ_WORK_BUSY. > > While we're at it: use the BIT() macro for all

Re: drm/mtrr: possible deadlock

Hi Dmitry, At 08/15/2017 03:18 PM, Dmitry Vyukov wrote: Hello, I am getting the following deadlock report while booting linux-next on 91dfed74eabcdae9378131546c446442c29bf769 in qemu. Config is attached. WARNING: possible recursive locking detected 4.13.0-rc4-next-20170811 #2 Not tainted

WARNING: CPU: 3 PID: 2952 at drivers/base/firmware_class.c:1225 _request_firmware+0x329/0x890

Hi! My new Thinkpad T470p regularly triggers this warning. Seems to happy only after resuming from suspend. [147242.220708] PM: Finishing wakeup. [147242.220711] OOM killer enabled. [147242.220711] Restarting tasks ... [147242.221908] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38

Re: [v3 1/2] sched/clock: interface to allow timestamps early in boot

Hi Pasha, At 08/14/2017 11:44 PM, Pasha Tatashin wrote: Hi Dou, Thank you for your comments: { x86_init.timers.timer_init(); tsc_init(); +tsc_early_fini(); tsc_early_fini() is defined in patch 2, I guess you may miss it when you split your patches. Indeed, I will move it

Re: [RESEND PATCH 2/2] gpio: aspeed: Remove reference to clock name in debounce warning message

On Tue, Aug 8, 2017 at 8:16 AM, Andrew Jeffery wrote: > HPLL was in fact not the clock we need. Remove description of which > clock to avoid any further error. > > Signed-off-by: Andrew Jeffery Patch applied with Joel's ACK. Yours, Linus Walleij

Re: [v6 05/15] mm: don't accessed uninitialized struct pages

[CC Mel - the original patch was http://lkml.kernel.org/r/1502138329-123460-6-git-send-email-pasha.tatas...@oracle.com] On Mon 07-08-17 16:38:39, Pavel Tatashin wrote: > In deferred_init_memmap() where all deferred struct pages are initialized > we have a check like this: > > if

Re: [PATCH v4 0/3] Introduce USB charger support in USB phy

Hi, Baolin Wang writes: >> Currently the Linux kernel does not provide any standard integration of this >> feature that integrates the USB subsystem with the system power regulation >> provided by PMICs meaning that either vendors must add this in their kernels >> or USB

[patch v3 1/3] drivers: jtag: Add JTAG core driver

Initial patch for JTAG friver JTAG class driver provide infrastructure to support hardware/software JTAG platform drivers. It provide user layer API interface for flashing and debugging external devices which equipped with JTAG interface using standard transactions. Driver exposes set of IOCTL to

[patch v3 0/3] JTAG driver introduction

When a need raise up to use JTAG interface for system's devices programming or CPU debugging, it could be done from the external JTAG master controller. For such purpose, usually the user layer application implements jtag protocol or using a proprietary connection to vendor hardware. This method

[patch v3 3/3] doccumentation: jtag: Add bindings for Aspeed SoC 24xx and 25xx families JTAG master driver

It has been tested on Mellanox system with BMC equipped with Aspeed 2520 SoC for programming CPLD devices. Signed-off-by: Oleksandr Shamray Signed-off-by: Jiri Pirko --- v2->v3 Comments pointed by Rob Herring - split Aspeed jtag

[PATCH v2] f2fs-tools: fix the usage message of overprovision option

The usage message shows a wrong message for ovp option, so fix it. Signed-off-by: Yunlong Song --- mkfs/f2fs_format_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mkfs/f2fs_format_main.c b/mkfs/f2fs_format_main.c index a3652a9..3279829 100644

Re: [RFC PATCH 3/7] mmc: sdhci: Add callback to set bus mode

On 07/08/17 19:01, Kishon Vijay Abraham I wrote: > Add callback to set bus mode in sdhci library so that the > controller driver can perform any bus mode specific configurations > in the callback function. A quirk isn't needed. Just hook ->set_ios() e.g. host->mmc_host_ops.set_ios =

[PATCH] ASoC: mediatek: Correct the interrupt property

This patch update interrupt property since we only use ASYS IRQ in the driver, and this may confuse people. Signed-off-by: Ryder Lee CC: Garlic Tseng --- Documentation/devicetree/bindings/sound/mt2701-afe-pcm.txt | 5 ++--- 1 file changed, 2

Re: [PATCH v1 1/4] KVM: MMU: check guest CR3 reserved bits based on its physical address width.

On 8/15/2017 12:40 AM, Paolo Bonzini wrote: On 14/08/2017 18:13, Jim Mattson wrote: ctxt->ops->get_msr(ctxt, MSR_EFER, ); - if (efer & EFER_LMA) - rsvd = CR3_L_MODE_RESERVED_BITS & ~CR3_PCID_INVD; + if (efer & EFER_LMA) { +

Re: [PATCH 01/11] ASoC: codecs: make snd_soc_platform_driver const

On Mon, Aug 14, 2017 at 05:08:40PM +0530, Bhumika Goyal wrote: > Make these const as they are either passed as the 2nd argument to the > function devm_snd_soc_register_platform or snd_soc_register_platform, > and the arguments are of type const. > Done using Coccinelle. > > Signed-off-by: Bhumika

[PATCH 1/1] Revert "mfd: da9061: Fix to remove BBAT_CONT register from chip model"

This patch was applied to the MFD twice, causing unwanted behavour. This reverts commit b77eb79acca3203883e8d8dbc7f2b842def1bff8. Fixes: b77eb79acca3 ("mfd: da9061: Fix to remove BBAT_CONT register from chip model") Reported-by: Steve Twiss Signed-off-by: Lee

[PATCH v2 0/2] Avoid system abort by moving pm domain's detach after devres_release_all

CONFIG_DEBUG_SHIRQ will fire extra irq action to call the registered irq callback after driver is removed or failed to probe. In general, the irq callback provided by driver should read its internal registers to see who fires the irq. So this leads a situation that we access the registers with a

[PATCH v2 2/2] mmc: dw_mmc: fix potential system abort if activating CONFIG_DEBUG_SHIRQ

With CONFIG_DEBUG_SHIRQ enabled, the irq tear down routine would still access the irq handler registed as a shard irq. Per the comment within the function of __free_irq, it says "It's a shared IRQ -- the driver ought to be prepared for an IRQ event to happen even now it's being freed". However

[PATCH v2 1/2] driver core: detach device's pm_domain after devres_release_all

Move dev_pm_domain_detach after devres_release_all to avoid accessing device's registers with genpd been powered off. Signed-off-by: Shawn Lin --- Changes in v2: None drivers/base/dd.c | 35 ++- drivers/base/platform.c | 18

Re: [PATCH v2 0/5] fs, xfs: block map immutable files for dax, dma-to-storage, and swap

On Mon 14-08-17 09:14:42, Dan Williams wrote: > On Mon, Aug 14, 2017 at 5:40 AM, Jan Kara wrote: > > On Sun 13-08-17 13:31:45, Dan Williams wrote: > >> On Sun, Aug 13, 2017 at 2:24 AM, Christoph Hellwig wrote: > >> > Thay being said I think we absolutely should support

Re: [PATCH] HID: input: throttle battery uevents

On Thu, 10 Aug 2017, Dmitry Torokhov wrote: > The power_supply subsystem tends to emit uevent every time > power_supply_changed() is called, so we should call this API only when > battery strength reported by the device is actually different from the > previous readings, otherwise we'll drown the

Re: [PATCH] mtd: plat-ram: use release_mem_region instead of release_resource

Le Fri, 11 Aug 2017 15:55:03 +0300, Anton Vasilyev a écrit : > Use api pair of request_mem_region and release_mem_region > instead of release_resource. > > Found by Linux Driver Verification project (linuxtesting. > > Signed-off-by: Anton Vasilyev > ---

[PATCH 0/3] constify snd_rawmidi_ops structures

These snd_rawmidi_ops structures are only passed as the third argument of snd_rawmidi_set_ops. This argument is const, so the snd_rawmidi_ops structures can be const too. Done with the help of Coccinelle. --- drivers/hid/hid-prodikeys.c |2 +- drivers/usb/gadget/function/f_midi.c

[RFC/PATCH v2] arm64: define MODULES_VADDR by module_alloc_base

After the kernel ASLR, the module virtual address is moved to [module_alloc_base, module_alloc_base + MODULES_VSIZE). However, the MODULES_VADDR is still defined as a constant and functions like is_vmalloc_or_module_addr() and dump function will not able to use correct module range information.

[PATCH v3 8/9] soc: mediatek: pwrap: add support for MT7622 SoC

From: Chenglin Xu Add the registers, callbacks and data structures required to make the PMIC wrapper work on MT7622. Signed-off-by: Chenglin Xu Signed-off-by: Chen Zhong Signed-off-by: Sean Wang

[PATCH v3 4/9] soc: mediatek: pwrap: add pwrap_read32 for reading in 32-bit mode

From: Sean Wang Some regulators such as MediaTek MT6380 has to be read in 32-bit mode. So the patch adds pwrap_read32, rename old pwrap_read into pwrap_read16 and one function pointer is introduced for increasing flexibility allowing the determination which mode is used

[PATCH v3 6/9] soc: mediatek: pwrap: update pwrap_init without slave programming

From: Sean Wang pwrap initialization is highly associated with the base SoC, so update here for allowing pwrap_init without slave program which would be used to those PMICs without extra encryption on bus such as MT6380. Signed-off-by: Chenglin Xu

[PATCH v3 9/9] soc: mediatek: pwrap: fixup warnings from coding style

From: Sean Wang fixup those warnings such as lines over 80 words and parenthesis alignment which would be complained by checkpatch.pl. Signed-off-by: Sean Wang --- drivers/soc/mediatek/mtk-pmic-wrap.c | 20 +--- 1 file changed,

Re: [PATCH v4 0/3] Improve readbility of NVME "wwid" attribute (target side)

For the series, Reviewed-by: Sagi Grimberg

Re: [PATCH v4 3/3] fs, xfs: introduce MAP_DIRECT for creating block-map-sealed file ranges

On Mon, Aug 14, 2017 at 11:12:22PM -0700, Dan Williams wrote: > MAP_DIRECT is an mmap(2) flag with the following semantics: > > MAP_DIRECT > In addition to this mapping having MAP_SHARED semantics, successful > faults in this range may assume that the block map (logical-file-offset > to

Re: [PATCH V3 1/2] pinctrl: qcom: spmi-gpio: Add support for GPIO LV/MV subtype

On Tue, Aug 15, 2017 at 2:38 AM, wrote: > From: Fenglin Wu > > GPIO LV (low voltage)/MV (medium voltage) subtypes have different > features and register mappings than 4CH/8CH subtypes. Add support > for LV and MV subtypes. > > Signed-off-by:

Re: [PATCH V3 2/2] pinctrl: qcom: spmi-gpio: Add dtest route for digital input

On Tue, Aug 15, 2017 at 2:38 AM, wrote: > From: Fenglin Wu > > Add property "qcom,dtest-buffer" to specify which dtest rail to feed > when the pin is configured as a digital input. > > Signed-off-by: Fenglin Wu >

Re: [PATCH 0/3] livepatch: introduce atomic replace

On Thu, 10 Aug 2017, Jason Baron wrote: > > > On 08/10/2017 07:12 AM, Miroslav Benes wrote: > > > > > Ok - associating the "atomic replace" with the patch itself makes sense to > > > me. > > > It would also basically work, I think with the patch I proposed except for > > > the > > > case where

Re: [RESEND PATCH 1/2] dt-bindings: gpio: aspeed: Remove reference to clock name

On Tue, Aug 8, 2017 at 8:16 AM, Andrew Jeffery wrote: > HPLL was in fact not the clock we need. Remove prescription of which > clock to avoid further error. Please refer to your datasheet and double > check like I should have. > > Signed-off-by: Andrew Jeffery

Re: [PATCH 3/3] ALSA: firewire-motu: constify snd_rawmidi_ops structures

On Tue, 15 Aug 2017 11:00:17 +0200, Julia Lawall wrote: > > > > On Tue, 15 Aug 2017, Takashi Iwai wrote: > > > On Tue, 15 Aug 2017 10:09:54 +0200, > > Julia Lawall wrote: > > > > > > These snd_rawmidi_ops structures are only passed as the third > > > argument of snd_rawmidi_set_ops. This

Re: [v6 15/15] mm: debug for raw alloctor

On Mon 14-08-17 10:01:52, Pasha Tatashin wrote: > >>However, now thinking about it, I will change it to CONFIG_MEMBLOCK_DEBUG, > >>and let users decide what other debugging configs need to be enabled, as > >>this is also OK. > > > >Actually the more I think about it the more I am convinced that a

RE: [PATCH 1/3] ACPICA: Dispatch active GPEs at init time

Hi, > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net] > Subject: Re: [PATCH 1/3] ACPICA: Dispatch active GPEs at init time > > On Friday, August 11, 2017 7:40:56 AM CEST Zheng, Lv wrote: > > Hi, Rafael > > > > > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net] > > > Subject: Re: [PATCH

Re: [RFC PATCH] media: vb2: add bidirectional flag in vb2_queue

On 08/14/17 10:41, Stanimir Varbanov wrote: > Hi, > > This RFC patch is intended to give to the drivers a choice to change > the default behavior of the v4l2-core DMA mapping direction from > DMA_TO/FROM_DEVICE (depending on the buffer type CAPTURE or OUTPUT) > to DMA_BIDIRECTIONAL during

[PATCH] usb: gadget: dummy: fix infinite loop because of missing loop decrement

From: Colin Ian King The while loop never terminates because the loop counter i is never decremented. Fix this by decrementing i. Detected by CoverityScan, CID#751073 ("Infinite Loop") Signed-off-by: Colin Ian King ---

Re: early x86 unseeded randomness

* Willy Tarreau wrote: > Nowadays we could use similar methods using RDTSC providing more accurate > counting. This doesn't provide a lot of entropy of course, given that a > 2 GHz machine will at most count 31 bits there. But I tend to think that > what matters during early boot

Re: [RFC PATCH 2/7] mmc: sdhci: Add quirk to indicate controller supports ADMA2

On 07/08/17 19:01, Kishon Vijay Abraham I wrote: > TI's implementation of sdhci controller used in DRA7 SoC's doesn't > have SDHCI_CAN_DO_ADMA2 set in CAPA register though it supports > ADMA2. Add quirk to support using ADMA2 even if the controller reports > incorrect capability in CAPA. A quirk

Re: [PATCH] rtc: rtctest: Improve support detection

Dne 12.8.2017 v 22:22 Alexandre Belloni napsal(a): > Hi, > > On 11/08/2017 at 11:14:55 +0200, Lukáš Doktor wrote: >> The rtc-generic and opal-rtc are failing to run this test as they do not >> support all the features. Let's treat the error returns and skip to the >> following test. >> >>

Re: [PATCH v2 2/3] mfd: tps65010: move header file out of I2C realm

On Mon, 14 Aug 2017, Wolfram Sang wrote: > include/linux/i2c is not for client devices. Move the header file to a > more appropriate location. > > Signed-off-by: Wolfram Sang > Acked-by: Greg Kroah-Hartman > Acked-by: Krzysztof Kozlowski

[PATCH 2/3] HID: prodikeys: constify snd_rawmidi_ops structures

This snd_rawmidi_ops structure is only passed as the third argument of snd_rawmidi_set_ops. This argument is const, so the snd_rawmidi_ops structure can be const too. Done with the help of Coccinelle. Signed-off-by: Julia Lawall --- drivers/hid/hid-prodikeys.c |2 +-

[PATCH 1/2] mm: Change the call sites of numa statistics items

In this patch, NUMA statistics is separated from zone statistics framework, all the call sites of NUMA stats are changed to use numa-stats-specific functions, it does not have any functionality change except that the value of NUMA stats is shown behind zone page stats, and the threshold size of

[PATCH v2 1/1] rtc: rtctest: Improve support detection

The rtc-generic and opal-rtc are failing to run this test as they do not support all the features. Let's treat the error returns and skip to the following test. Theoretically the test_DATE should be also adjusted, but as it's enabled on demand I think it makes sense to fail in such case.

Re: random.c: LFSR polynomials are not irreducible/primitive

Am Dienstag, 15. August 2017, 00:21:05 CEST schrieb Theodore Ts'o: Hi Theodore, > Have you looked at section 3.1.1 of the above cited paper? > > http://eprint.iacr.org/2012/251.pdf Thanks for the hint, but that does not seem to solve the mystery either. When I use magma with GF(2^32), I

[PATCH v2 0/1] rtc: rtctest: Support opal-rtc and rtc-generic

On ppc64le machines the opal-rtc, resp rtc-generic in guest is used. They only support minimal set of functionality and fail this test in not-yet treated way. This extends the checks and skips to the next test when feature is not supported. Changes in v2: - Removed the double EINVAL check - Added

[PATCH 2/2] mm: Update NUMA counter threshold size

There is significant overhead in cache bouncing caused by zone counters (NUMA associated counters) update in parallel in multi-threaded page allocation (suggested by Dave Hansen). This patch updates NUMA counter threshold to a fixed size of 32765, as a small threshold greatly increases the update

[PATCH 0/2] Separate NUMA statistics from zone statistics

Each page allocation updates a set of per-zone statistics with a call to zone_statistics(). As discussed in 2017 MM submit, these are a substantial source of overhead in the page allocator and are very rarely consumed. This significant overhead in cache bouncing caused by zone counters (NUMA

Re: [PATCH v5] clk: sunxi-ng: support R40 SoC

在 2017-08-15 13:55，Icenowy Zheng 写道： Allwinner R40 SoC have a clock controller module in the style of the SoCs beyond sun6i, however, it's more rich and complex. Add support for it. Signed-off-by: Icenowy Zheng --- Changes in v5: - Added TODO's for PLL constraints. - Forced

[tip:x86/asm] x86/xen/64: Fix the reported SS and CS in SYSCALL

Commit-ID: fa2016a8e7d846b306e431646d250500e1da0c33 Gitweb: http://git.kernel.org/tip/fa2016a8e7d846b306e431646d250500e1da0c33 Author: Andy Lutomirski AuthorDate: Mon, 14 Aug 2017 22:36:19 -0700 Committer: Ingo Molnar CommitDate: Tue, 15 Aug 2017

Re: [PATCH v4 0/3] MAP_DIRECT and block-map sealed files

On Mon, Aug 14, 2017 at 11:12:05PM -0700, Dan Williams wrote: > Changes since v3 [1]: > * Move from an fallocate(2) interface to a new mmap(2) flag and rename > 'immutable' to 'sealed'. > > * Do not record the sealed state in permanent metadata it is now purely > a temporary state for as long

Re: [PATCH] HID: sensor: constify platform_device_id

On Sun, 13 Aug 2017, Arvind Yadav wrote: > platform_device_id are not supposed to change at runtime. All functions > working with platform_device_id provided by > work with const platform_device_id. So mark the non-const structs as > const. > > Signed-off-by: Arvind Yadav

[PATCH v3 5/9] soc: mediatek: pwrap: add pwrap_write32 for writing in 32-bit mode

From: Sean Wang Some regulators such as MediaTek MT6380 also has to be written in 32-bit mode. So the patch adds pwrap_write32, rename old pwrap_write into pwrap_write16 and one additional function pointer is introduced for increasing flexibility allowing the

[PATCH v3 3/9] regulator: mt6380: Add support for MT6380

From: Chenglin Xu The MT6380 is a regulator found those boards with MediaTek MT7622 SoC It is connected as a slave to the SoC using MediaTek PMIC wrapper which is the common interface connecting with Mediatek made various PMICs. Signed-off-by: Chenglin Xu

[PATCH v3 2/9] dt-bindings: regulator: Add document for MediaTek MT6380 regulator

From: Sean Wang add dt-binding document for MediaTek MT6380 PMIC Signed-off-by: Chenglin Xu Signed-off-by: Sean Wang --- .../bindings/regulator/mt6380-regulator.txt| 89 ++ 1 file changed,

[PATCH v3 1/9] dt-bindings: arm: mediatek: add MT7622 string to the PMIC wrapper doc

From: Sean Wang Signed-off-by: Chenglin Xu Signed-off-by: Sean Wang Acked-by: Rob Herring --- Documentation/devicetree/bindings/soc/mediatek/pwrap.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCHv3] perf bpf: Fix endianness problem when loading parameters in prologue

Perf BPF prologue generator unconditionally fetches 8 bytes for function parameters, which causes problem on big endian machine. Thomas gives a detail analysis for this problem: http://lkml.kernel.org/r/968ebda5-abe4-8830-8d69-49f62529d...@linux.vnet.ibm.com This patch parses the type of each

Re: [PATCH 1/3] thunderbolt: Remove superfluous check

On Tue, Aug 15, 2017 at 8:19 AM, Bernat, Yehezkel wrote: > The key size is tested by hex2bin() already (as '\0' isn't an hex digit) Yes, and it's guaranteed (by kernelfs) that '\0' will be there sooner or later. > Suggested-by: Andy Shevchenko

Re: [PATCH 0/5] perf script: Add support for exporting to sqlite3

On 03/08/17 11:31, Adrian Hunter wrote: > Hi > > Here is a script for exporting to SQLite 3 the same data as the PostgreSQL > export. The call-graph script is renamed and amended to work with both > PostgreSQL and SQLite. > > > Adrian Hunter (5): > perf script: Fix missing call_path_id

Re: [kernel-hardening] [PATCH v5 07/10] arm64/mm: Don't flush the data cache if the page is unmapped by XPFO

On Mon, Aug 14, 2017 at 02:27:27PM -0600, Tycho Andersen wrote: > Hi Mark, > > First, thanks for taking a look! > > On Sat, Aug 12, 2017 at 12:57:37PM +0100, Mark Rutland wrote: > > On Wed, Aug 09, 2017 at 02:07:52PM -0600, Tycho Andersen wrote: > > > From: Juerg Haefliger

[PATCH 2/3] dt-bindings: regulator: add fixes with MT6323 dt-bindings shouldn't reference driver

From: Sean Wang DT bindings shouldn't reference drivers and they should be OS-agnostic. Signed-off-by: Sean Wang --- Documentation/devicetree/bindings/regulator/mt6323-regulator.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH 1/3] dt-bindings: regulator: add fixes with MT6311 dt-bindings shouldn't reference driver

From: Sean Wang DT bindings shouldn't reference drivers and they should be OS-agnostic. Signed-off-by: Sean Wang --- Documentation/devicetree/bindings/regulator/mt6311-regulator.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH 3/3] dt-bindings: regulator: add fixes with MT6397 dt-bindings shouldn't reference driver

From: Sean Wang DT bindings shouldn't reference drivers and they should be OS-agnostic. Signed-off-by: Sean Wang --- Documentation/devicetree/bindings/regulator/mt6397-regulator.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH] acpi/processor: make function acpi_processor_check_duplicates static

From: Colin Ian King The function acpi_processor_check_duplicates is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warnings: symbol 'acpi_processor_check_duplicates' was not declared. Should it be static?

Re: [PATCH 1/2] mm: Change the call sites of numa statistics items

On Tue, Aug 15, 2017 at 04:45:35PM +0800, Kemi Wang wrote: > In this patch, NUMA statistics is separated from zone statistics > framework, all the call sites of NUMA stats are changed to use > numa-stats-specific functions, it does not have any functionality change > except that the value of NUMA

Re: [PATCH v2 4/5] usb: gadget: udc: Replace the deprecated extcon API

Hi, Chanwoo Choi writes: > This patch replaces the deprecated extcon API as following: > - extcon_get_cable_state_() -> extcon_get_state() > > Cc: Felipe Balbi > Cc: Greg Kroah-Hartman > Cc: Raviteja Garimella

Re: [PATCH 2/2] mm: Update NUMA counter threshold size

On Tue, Aug 15, 2017 at 04:45:36PM +0800, Kemi Wang wrote: > Threshold CPU cyclesThroughput(88 threads) > 32 799 241760478 > 64 640 301628829 > 125 537 358906028 <==> system by default (base) > 256 468

Re: [RFC PATCH] media: vb2: add bidirectional flag in vb2_queue

On Mon, Aug 14, 2017 at 11:41:55AM +0300, Stanimir Varbanov wrote: > Hi, > > This RFC patch is intended to give to the drivers a choice to change > the default behavior of the v4l2-core DMA mapping direction from > DMA_TO/FROM_DEVICE (depending on the buffer type CAPTURE or OUTPUT) > to

Re: A udev rule to serve the change event of ACPI container?

On Fri, Aug 04, 2017 at 05:06:19PM +0200, Michal Hocko wrote: > On Thu 03-08-17 11:37:37, YASUAKI ISHIMATSU wrote: > > > > > > On 08/02/2017 01:49 AM, joeyli wrote: > > > Hi YASUAKI, > > > > > > On Tue, Aug 01, 2017 at 03:21:38PM -0400, YASUAKI ISHIMATSU wrote: > > >> Hi Joey, > > >> > > >> On

Re: [PATCH] usb: gadget: udc: udc_stop before gadget unbind

Hi, Danilo Krummrich writes: > udc_stop needs to be called before gadget driver unbind. Otherwise it > might happen that udc drivers still call into the gadget driver (e.g. > to reset gadget after OTG event). If this happens it is likely to get > panics from

[PATCH] crypto: rockchip: Don't dequeue the request when device is busy

The device can only process one request at a time. So if multiple requests came at the same time, we can enqueue them first, and dequeue them one by one when the device is idle. Signed-off-by: zain wang --- drivers/crypto/rockchip/rk3288_crypto.c| 46 ++-

Re: [RFC PATCH 4/7] mmc: sdhci: Add quirk to indicate broken POWER_CONTROL

On 07/08/17 19:01, Kishon Vijay Abraham I wrote: > TI's implementation of sdhci controller used in DRA7 SoC's uses > POWER_CONTROL register for configuring IO voltage and not > for core voltage (vdd) which is it's intended use. Add a quirk > to indicate broken POWER_CONTROL register. A quirk

Re: early x86 unseeded randomness

* Willy Tarreau wrote: > On Tue, Aug 15, 2017 at 09:42:54AM +0200, Ingo Molnar wrote: > > > > * Willy Tarreau wrote: > > > > > Nowadays we could use similar methods using RDTSC providing more accurate > > > counting. This doesn't provide a lot of entropy of course,

Re: [PATCH v8 00/14] lockdep: Implement crossrelease feature

So with the latest fixes there's a new lockdep warning on one of my testboxes: [ 11.322487] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ 11.495661] == [ 11.502093] WARNING: possible circular locking

[GIT PULL] Immutable branch between MFD, ARM, USB and Video due for the v4.14 merge window

Enjoy! The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877: Linux v4.13-rc1 (2017-07-15 15:22:10 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/ib-mfd-arm-usb-video-v4.14 for you to fetch changes up to

Re: [RFC PATCH 6/7] mmc: sdhci-omap: Add OMAP SDHCI driver

On 07/08/17 19:01, Kishon Vijay Abraham I wrote: > Create a new sdhci-omap driver to configure the eMMC/SD/SDIO controller > in TI's OMAP SoCs making use of the SDHCI core library. For OMAP specific > configurations, populate sdhci_ops with OMAP specific callbacks and use > SDHCI quirks. > Enable

Re: [RFC GIT PULL rcu/next] RCU/hotplug fix

* Paul E. McKenney wrote: > Hello, Ingo, > > This pull request is for an RCU change that permits waiting for grace > periods started by CPUs late in the process of going offline. Lack of > this capability is causing failures: > >

[tip:core/rcu] rcu: Migrate callbacks earlier in the CPU-offline timeline

Commit-ID: a58163d8ca2c8d288ee9f95989712f98473a5ac2 Gitweb: http://git.kernel.org/tip/a58163d8ca2c8d288ee9f95989712f98473a5ac2 Author: Paul E. McKenney AuthorDate: Tue, 20 Jun 2017 12:11:34 -0700 Committer: Paul E. McKenney

Re: [PATCHv2] perf bpf: Fix endianness problem when loading parameters in prologue

On 2017/8/15 14:42, Thomas-Mich Richter wrote: On 08/14/2017 06:39 PM, Arnaldo Carvalho de Melo wrote: Em Mon, Aug 14, 2017 at 01:46:44PM +0200, Thomas Richter escreveu: Perf BPF prologue generator unconditionally fetches 8 bytes for function parameters, which causes problem on big endian

Re: [PATCH 3/3] ALSA: firewire-motu: constify snd_rawmidi_ops structures

On Tue, 15 Aug 2017, Takashi Iwai wrote: > On Tue, 15 Aug 2017 10:09:54 +0200, > Julia Lawall wrote: > > > > These snd_rawmidi_ops structures are only passed as the third > > argument of snd_rawmidi_set_ops. This argument is const, so the > > snd_rawmidi_ops structures can be const too. > > >

<    2   3   4   5   6   7   8   9   10   11   >