Re: [PATCH] USB: announce bcdDevice as well as idVendor, idProduct.

On Fri, Mar 23, 2018 at 5:33 PM, Benson Leung wrote: > Print bcdDevice which is used by vendors to identify different versions > of the same product (or different versions of firmware). > > Adding this to the logs will be useful for support purposes. > > Signed-off-by: Benson

Re: [PATCH 00/11] Use global pages with PTI

On Fri, Mar 23, 2018 at 5:46 PM, Linus Torvalds wrote: > > It is, of course, possible that I misunderstood what you actually > benchmarked. But I assume the above benchmark numbers are with the > whole "don't even do global entries if you have PCID". Oh, I went

Re: [PATCH v3 2/2] x86, cpuid: allow cpuid_read() to schedule

On 03/23/2018 03:17 PM, H. Peter Anvin wrote: > On 03/23/18 14:58, Eric Dumazet wrote: >> I noticed high latencies caused by a daemon periodically reading various >> MSR and cpuid on all cpus. KASAN kernels would see ~10ms latencies >> simply reading one cpuid. Even without KASAN, sending IPI to

Re: [PATCH] USB: announce bcdDevice as well as idVendor, idProduct.

On Fri, Mar 23, 2018 at 5:48 PM, Andrew Chant wrote: > On Fri, Mar 23, 2018 at 5:33 PM, Benson Leung wrote: >> Print bcdDevice which is used by vendors to identify different versions >> of the same product (or different versions of firmware). >> >> Adding

Re: [RFC PATCH 5/6] sched/fair: Select an energy-efficient CPU on task wake-up

Hi Morten, On Fri, Mar 23, 2018 at 8:47 AM, Morten Rasmussen wrote: > On Thu, Mar 22, 2018 at 01:10:22PM -0700, Joel Fernandes wrote: >> On Wed, Mar 21, 2018 at 8:35 AM, Patrick Bellasi >> wrote: >> > [...] >> > >> >> @@ -6555,6 +6613,14 @@

Re: ftrace on MIPS/ath79

On Fri, 23 Mar 2018 23:20:10 +0100 Matthias Schiffer wrote: > Hi, > I'm currently trying to debug a performance bottleneck on low-end ath79 > hardware running OpenWrt/LEDE, but it seems that ftrace is not working > correctly on these systems. I have tried this

Re: [PATCH 02/10] kbuild: clean up *.lex.c and *.tab.[ch] patterns from top-level Makefile

On 03/23/18 06:04, Masahiro Yamada wrote: > Files suffixed by .lex.c, .tab.[ch] are generated lexers, parsers, > respectively. Clean them up globally from the top Makefile. > > Some of the final host programs they are linked into are needed for > building external modules, but those

Re: [PATCH 04/10] kbuild: add %.lex.c and %.tab.[ch] to 'targets' automatically

On 03/23/18 06:04, Masahiro Yamada wrote: > Files generated by if_changed* must be added to 'targets' to include > *.cmd files. Otherwise, they would be regenerated every time. > > The build system automatically adds objects to 'targets' where > appropriate, such as obj-y, extra-y, etc. but does

Re: rcu: Add might_sleep() check to synchronize_rcu()

On Fri, 23 Mar 2018 15:57:04 -0700 Joel Fernandes wrote: > > diff --git a/net/l2tp/l2tp_core.c b/net/l2tp/l2tp_core.c > > index 194a7483bb93..857b494bee29 100644 > > --- a/net/l2tp/l2tp_core.c > > +++ b/net/l2tp/l2tp_core.c > > @@ -1677,6 +1677,8 @@ void

Re: [RFC PATCH 5/6] sched/fair: Select an energy-efficient CPU on task wake-up

On Friday 23 Mar 2018 at 15:47:45 (+), Morten Rasmussen wrote: > On Thu, Mar 22, 2018 at 01:10:22PM -0700, Joel Fernandes wrote: > > On Wed, Mar 21, 2018 at 8:35 AM, Patrick Bellasi > > wrote: > > > [...] > > > > > >> @@ -6555,6 +6613,14 @@ select_task_rq_fair(struct

Re: [PATCH 05/10] kbuild: add %.dtb.S and %.dtb to 'targets' automatically

On 03/23/18 06:04, Masahiro Yamada wrote: > Another common pattern that consists of chained commands is to compile > a DTB as binary data into the kernel image or a module. It is used in > several places in the source tree. Let's support it in the build core. > > $(call if_changed,dt_S_dtb) is

Re: [PATCH 10/10] kbuild: mark $(targets) as .SECONDARY and remove .PRECIOUS specifier

On 03/23/18 06:04, Masahiro Yamada wrote: > GNU Make automatically deletes intermediate files that are updated > in a chain of pattern rules. > > Example 1) %.dtb.o <- %.dtb.S <- %.dtb.S <- %.dts > Example 2) %.o <- %.c <- %.c_shipped > > A couple of makefiles mark such targets as .PRECIOUS to

Re: [PATCH 01/10] .gitignore: move *.lex.c *.tab.[ch] patterns to the top-level .gitignore

On 03/23/18 06:04, Masahiro Yamada wrote: > These patterns are common to host programs that require lexer and parser. > Move them to the top .gitignore. > > Signed-off-by: Masahiro Yamada Acked-by: Frank Rowand -Frank > --- > >

[PATCH v2] USB: announce bcdDevice as well as idVendor, idProduct.

Print bcdDevice which is used by vendors to identify different versions of the same product (or different versions of firmware). Adding this to the logs will be useful for support purposes. Match the %2x.%02x formatting that's used by lsusb -v for this same value. Signed-off-by: Benson Leung

Re: [PATCH] [RFC] drm: rcar-du: keep temporary dtb files around during build

Hi Geert, On 03/22/18 07:26, Geert Uytterhoeven wrote: > Hi Frank, > > On Fri, Mar 16, 2018 at 2:39 AM, wrote: >> On Thursday, March 15, 2018 8:37 AM, Arnd Bergmann [mailto:a...@arndb.de] >> wrote: >>> >>> The *.dtb and *.dtb.S files get removed by 'make' during the

Re: [RFC PATCH 5/6] sched/fair: Select an energy-efficient CPU on task wake-up

On Friday 23 Mar 2018 at 18:13:56 (-0700), Joel Fernandes wrote: > Hi Morten, > > On Fri, Mar 23, 2018 at 8:47 AM, Morten Rasmussen > wrote: > > On Thu, Mar 22, 2018 at 01:10:22PM -0700, Joel Fernandes wrote: [...] > > You mean if SD_BALANCE_WAKE isn't set on

Re: [PATCH] USB: announce bcdDevice as well as idVendor, idProduct.

On Fri, Mar 23, 2018 at 06:08:07PM -0700, Andrew Chant wrote: > >> +"New USB device found, idVendor=%04x, idProduct=%04x, > >> bcdDevice=%04x\n", > > Can you please decode bcdDevice into a decimal string? > > > > lsusb -v does this (bcdDevice: 0.03 for example) and in my

Re: [RFC PATCH 5/6] sched/fair: Select an energy-efficient CPU on task wake-up

On Thursday 22 Mar 2018 at 13:19:03 (-0700), Joel Fernandes wrote: > On Thu, Mar 22, 2018 at 11:06 AM, Patrick Bellasi > wrote: [...] > >> > @@ -6555,6 +6613,14 @@ select_task_rq_fair(struct task_struct *p, int > >> > prev_cpu, int sd_flag, int wake_f > >> >

Re: [PATCH] [media] vcodec: fix error return value from mtk_jpeg_clk_init()

On Fri, 2018-03-23 at 11:44 +0800, Ryder Lee wrote: > The error return value should be fixed as it may return EPROBE_DEFER. > > Cc: Rick Chang > Cc: Bin Liu > Signed-off-by: Ryder Lee > --- >  

Re: [PATCH v5 00/13] ARM: dts: ipq: updates to enable a few peripherals

On Fri, Mar 23, 2018 at 03:48:43PM +0530, Sricharan R wrote: > [v5] > * Fixed a minor comment that i missed earlier. I tried booting this series with qcom_defconfig on my custom, dk07-like board. It works! Thanks a bunch, Richard

[REGRESSION v4.16-rc6] [PATCH] mqueue: forbid unprivileged user access to internal mount

Hi all, Felix reported weird behaviour on 4.16.0-rc6 with regards to mqueue[1], which was introduced by 36735a6a2b5e ("mqueue: switch to on-demand creation of internal mount"). Basically, the reproducer boils down to being able to mount mqueue if you create a new user namespace, even if you

[PATCH v8 14/14] iommu/rockchip: Support sharing IOMMU between masters

There would be some masters sharing the same IOMMU device. Put them in the same iommu group and share the same iommu domain. Signed-off-by: Jeffy Chen Reviewed-by: Robin Murphy --- Changes in v8: None Changes in v7: Use iommu_group_ref_get to

[PATCH v8 10/14] iommu/rockchip: Use IOMMU device for dma mapping operations

Use the first registered IOMMU device for dma mapping operations, and drop the domain platform device. This is similar to exynos iommu driver. Signed-off-by: Jeffy Chen Reviewed-by: Tomasz Figa Reviewed-by: Robin Murphy ---

[PATCH v8 06/14] iommu/rockchip: Fix TLB flush of secondary IOMMUs

From: Tomasz Figa Due to the bug in current code, only first IOMMU has the TLB lines flushed in rk_iommu_zap_lines. This patch fixes the inner loop to execute for all IOMMUs and properly flush the TLB. Signed-off-by: Tomasz Figa Signed-off-by: Jeffy Chen

[PATCH v8 07/14] ARM: dts: rockchip: add clocks in iommu nodes

Add clocks in iommu nodes, since we are going to control clocks in rockchip iommu driver. Signed-off-by: Jeffy Chen --- Changes in v8: None Changes in v7: None Changes in v6: Add clk names, and modify all iommu nodes in all existing rockchip dts Changes in v5: Remove

[PATCH v8 09/14] dt-bindings: iommu/rockchip: Add clock property

Add clock property, since we are going to control clocks in rockchip iommu driver. Signed-off-by: Jeffy Chen Reviewed-by: Robin Murphy --- Changes in v8: None Changes in v7: None Changes in v6: None Changes in v5: None Changes in v4: None

Re: [PATCH 2/2 v3] tpm: separate cmd_ready/go_idle from runtime_pm

On Mon, Mar 05, 2018 at 08:08:31PM +0200, Jarkko Sakkinen wrote: > On Tue, Feb 20, 2018 at 04:13:30PM +0200, Jarkko Sakkinen wrote: > > On Mon, 2018-02-19 at 13:52 +0200, Jarkko Sakkinen wrote: > > > On Wed, Feb 14, 2018 at 03:43:19PM +0200, Tomas Winkler wrote: > > > > We cannot use go_idle

Re: [PATCH v4 11/22] driver core: add per device iommu param

On Thu, Mar 22, 2018 at 08:12:03PM -0700, Jacob Pan wrote: > DMA faults can be detected by IOMMU at device level. Adding a pointer > to struct device allows IOMMU subsystem to report relevant faults > back to the device driver for further handling. > For direct assigned device (or user space

Re: [PATCH] ata: ahci-platform: add reset control support

Hi, On 23-03-18 02:30, Kunihiko Hayashi wrote: Add support to get and control a list of resets for the device as optional and shared. These resets must be kept de-asserted until the device is enabled. This is specified as shared because some SoCs like UniPhier series have common reset controls

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

* Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the tip tree got a conflict in: > > kernel/sched/cpufreq_schedutil.c > > between commit: > > 0953feed3400 ("cpufreq: schedutil: rate limits for SCHED_DEADLINE") Rafael, could you please send that

[PATCH v3 5/6] dt-bindings: phy-qcom-usb2: Update bindings for sdm845

Update compatible strings for USB2 PHYs on sdm845. There are two QUSB2 PHYs present on sdm845. Few PHY registers programming is different for these PHYs related to electrical parameters, otherwise both are same. Signed-off-by: Manu Gautam ---

[PATCH V3] Input: pm8941-pwrkey: add resin key capabilities

Add resin key support to handle different types of key events defined in different platforms. Signed-off-by: Tirupathi Reddy --- .../bindings/input/qcom,pm8941-pwrkey.txt | 32 + drivers/input/misc/pm8941-pwrkey.c | 81

Re: [PATCH 2/2] mmc: Add mmc_force_detect_change_begin / _end functions

Hi Uffe, On Fri, Feb 09, 2018 at 03:01:00PM +0100, Ulf Hansson wrote: > [...] > > >> > I'd like to know if any progress has been made on that problem (I may > >> > have missed patches). > >> > Had you had the time to look at the issue? > >> > >> I have looked at the issue, but not manage to cook

[PATCH v8 08/14] iommu/rockchip: Control clocks needed to access the IOMMU

From: Tomasz Figa Current code relies on master driver enabling necessary clocks before IOMMU is accessed, however there are cases when the IOMMU should be accessed while the master is not running yet, for example allocating V4L2 videobuf2 buffers, which is done by the VB2

[PATCH v8 05/14] iommu/rockchip: Use iopoll helpers to wait for hardware

From: Tomasz Figa This patch converts the rockchip-iommu driver to use the in-kernel iopoll helpers to wait for certain status bits to change in registers instead of an open-coded custom macro. Signed-off-by: Tomasz Figa Signed-off-by: Jeffy Chen

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

On 03/22/2018 10:01 PM, Alexandre Belloni wrote: > On 16/03/2018 at 07:34:06 +, Patrice CHOTARD wrote: >> Hi Arnd, Stephen >> >> On 03/15/2018 10:06 PM, Arnd Bergmann wrote: >>> On Thu, Mar 15, 2018 at 9:56 PM, Stephen Rothwell >>> wrote: Hi all, Commit

[PATCH v8 02/14] iommu/rockchip: Fix error handling in probe

Add missing iommu_device_sysfs_remove in error path. Signed-off-by: Jeffy Chen Reviewed-by: Tomasz Figa Acked-by: Robin Murphy --- Changes in v8: Don't introduce the additional return. Changes in v7: None Changes in v6:

[PATCH v8 01/14] iommu/rockchip: Prohibit unbind and remove

Removal of IOMMUs cannot be done reliably. This is similar to exynos iommu driver. Signed-off-by: Jeffy Chen Reviewed-by: Tomasz Figa Acked-by: Robin Murphy --- Changes in v8: Rebase on newest for-next. Changes in v7: None

[PATCH v8 04/14] iommu/rockchip: Fix error handling in attach

From: Tomasz Figa Currently if the driver encounters an error while attaching device, it will leave the IOMMU in an inconsistent state. Even though it shouldn't really happen in reality, let's just add proper error path to keep things consistent. Signed-off-by: Tomasz Figa

Re: [PATCH 3/4] mm: Add free()

On 2018-03-22 20:58, Matthew Wilcox wrote: > From: Matthew Wilcox > > free() can free many different kinds of memory. I'd be a bit worried about using that name. gcc very much knows about the C standard's definition of that function, as can be seen on godbolt.org by

Re: [PATCH V3] ZBOOT: fix stack protector in compressed boot phase

hen <che...@lemote.com> This patch breaks booting on ARM Exynos4210 based boards (tested with next-20180323, exynos_defconfig, both Trats and Origen fails to boot). That's a bit strange, because all other Exynos SoC works fine (I've checked 3250, 4412, 5250, 5410 and 542x). I really have no

Re: [PATCH v2] vmw_balloon: fixing double free when batching mode is off

Hi. On Thu, Mar 22, 2018 at 9:02 PM, Nadav Amit wrote: > Actually, rechecking the bug description, I might have rushed. The bug that > I encountered is related to the vunmap() but it is only caused when batching > is off, while the bug you reported has batching on. > > It seems

Re: [PATCH V2 3/4] clk: add managed version of clk_bulk_get_all

/commits/Dong-Aisheng/clk-new-APIs-to-handle-all-available-clocks/20180323-122451 base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next config: powerpc-defconfig (attached as .config) compiler: powerpc64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0 reproduce: wget https

Re: [PATCH v3 0/1] can: ucan: add driver for Theobroma Systems UCAN devices

Hello Jacob, Am 22.03.2018 um 14:53 schrieb Jakob Unterwurzacher: > This is v3 of the Theobroma Systems CAN/USB adapter driver > upstreaming effort. > > Featured v2 -> v3 changes: > * count error frames as data packets > * use canid_t for all can ids > * use BIT(x) instead of (1 << x) > * use

[PATCH net-next 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Add a new module crashdd that exports the /sys/kernel/crashdd/ directory in second kernel, containing collected hardware/firmware dumps. The sequence of actions done by device drivers to append their device specific hardware/firmware logs to /sys/kernel/crashdd/ directory are as follows: 1.

Re: [PATCH v6] ARM: dts: wheat: Fix ADV7513 address usage

On Thu, Mar 22, 2018 at 09:30:40PM +, Kieran Bingham wrote: > The r8a7792 Wheat board has two ADV7513 devices sharing a single I2C > bus, however in low power mode the ADV7513 will reset it's slave maps to > use the hardware defined default addresses. > > The ADV7511 driver was adapted to

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

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: fs/ocfs2/filecheck.c between commit: e24e960c7fe2 ("sched/wait, fs/ocfs2: Convert wait_on_atomic_t() usage to the new wait_var_event() API") from the tip tree and commit: 5a5b76d17dc4 ("ocfs2: add kobject

floating point computation error caused by eagerfpu

Hi, I'm trying to figure out the root cause of a floating point calculation error on kernel 4.4.98. My coworker runs a SHA1 test tool. The generated sha1 does not match the expected value. Strangely, this test just goes well on one VM. After a lot of comparison between this VM and the bare metal

[PATCH] Documentation: magic-numbers: Fix typo

This fixes a little then / them confusion. Signed-off-by: Martin Kepplinger --- Documentation/process/magic-number.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/process/magic-number.rst b/Documentation/process/magic-number.rst index

[PATCH v8 13/14] iommu/rockchip: Add runtime PM support

When the power domain is powered off, the IOMMU cannot be accessed and register programming must be deferred until the power domain becomes enabled. Add runtime PM support, and use runtime PM device link from IOMMU to master to enable and disable IOMMU. Signed-off-by: Jeffy Chen

[PATCH v8 03/14] iommu/rockchip: Request irqs in rk_iommu_probe()

Move request_irq to the end of rk_iommu_probe(). Suggested-by: Robin Murphy Signed-off-by: Jeffy Chen Acked-by: Robin Murphy --- Changes in v8: None Changes in v7: None Changes in v6: None Changes in v5: None Changes in

[PATCH v8 11/14] iommu/rockchip: Use OF_IOMMU to attach devices automatically

Converts the rockchip-iommu driver to use the OF_IOMMU infrastructure, which allows attaching master devices to their IOMMUs automatically according to DT properties. Signed-off-by: Jeffy Chen Reviewed-by: Robin Murphy --- Changes in v8: None

[PATCH v8 00/14] iommu/rockchip: Use OF_IOMMU

This series fixes some issues in rockchip iommu driver, and add of_iommu support in it. Changes in v8: Rebase on newest for-next. Don't introduce the additional return. Rename startup()/shutdown() to enable()/disable(). Do runtime PM suspend in .shutdown(). Modify

[PATCH v8 12/14] iommu/rockchip: Fix error handling in init

It's hard to undo bus_set_iommu() in the error path, so move it to the end of rk_iommu_probe(). Signed-off-by: Jeffy Chen Reviewed-by: Tomasz Figa Reviewed-by: Robin Murphy --- Changes in v8: None Changes in v7: None Changes

[PATCH v3 0/6] phy: qcom: Updates for USB PHYs on SDM845

SDM845 has two USB instances each with QUSB2 and QMP PHYs. One of the QMP PHY is USB-DP (DisplayPort) combo PHY where as other one is single lane UNI-PHY (without DP support). Changes are related to PHY configuration for electrical parameters tuning to improve eye-diagram and some fixes. Changes

[PATCH v3 4/6] phy: qcom-qmp: Add QMP V3 USB3 UNI PHY support for sdm845

QMP V3 UNI PHY is a single lane USB3 PHY without support for DisplayPort (DP). Main difference from DP combo QMPv3 PHY is that UNI PHY doesn't have dual RX/TX lanes and no separate DP_COM block for configuration related to type-c or DP. While at it, fix has_pwrdn_delay attribute for USB-DP PHY

[PATCH v3 1/6] phy: qcom-qmp: Enable pipe_clk before checking USB3 PHY_STATUS

QMP PHY for USB mode requires pipe_clk for calibration and PLL lock to take place. This clock is output from PHY to GCC clock_ctl and then fed back to QMP PHY and is available from PHY only after PHY is reset and initialized, hence it can't be enabled too early in initialization sequence.

[PATCH v3 2/6] phy: qcom-qusb2: Fix crash if nvmem cell not specified

Driver currently crashes due to NULL pointer deference while updating PHY tune register if nvmem cell is NULL. Since, fused value for Tune1/2 register is optional, we'd rather bail out. Fixes: ca04d9d3e1b1 ("phy: qcom-qusb2: New driver for QUSB2 PHY on Qcom chips") Reviewed-by: Vivek Gautam

[PATCH v3 3/6] dt-bindings: phy-qcom-qmp: Update bindings for sdm845

Update compatible strings for USB3 PHYs on SDM845. One is QMPv3 DisplayPort-USB combo PHY and other one is USB UNI PHY which is single lane USB3 PHY without DP capability. Reviewed-by: Rob Herring Signed-off-by: Manu Gautam ---

[PATCH v3 6/6] phy: qcom-qusb2: Add QUSB2 PHYs support for sdm845

There are two QUSB2 PHYs present on sdm845. Update PHY registers programming for both the PHYs related to electrical parameters to improve eye diagram. Signed-off-by: Manu Gautam --- drivers/phy/qualcomm/phy-qcom-qusb2.c | 39 +++ 1 file

linux-next: Tree for Mar 23

Hi all, Changes since 20180322: The vfs tree still had its build failure for which I reverted a commit. The tip tree gained a conflict against the pm tree. The akpm-current tree gained a conflict against the tip tree. Non-merge commits (relative to Linus' tree): 9556 11897 files changed,

Re: [RFC PATCH] nvme: avoid race-conditions when enabling devices

> On Wed, Mar 21, 2018 at 05:10:56PM +0100, Marta Rybczynska wrote: >> >> The problem may happen also with other device doing its probe and >> nvme running its workqueue (and we probably have seen it in practice >> too). We were thinking about a lock in the pci generic code too, >> that's why

Re: [PATCH v6 2/2] cpuset: Add cpuset.sched_load_balance to v2

On 22/03/18 17:50, Waiman Long wrote: > On 03/22/2018 04:41 AM, Juri Lelli wrote: > > On 21/03/18 12:21, Waiman Long wrote: [...] > >> + cpuset.sched_load_balance > >> + A read-write single value file which exists on non-root cgroups. > >> + The default is "1" (on), and the other possible

Re: [PATCH v2] crypto: talitos - fix IPsec cipher in length

On 3/22/2018 11:57 AM, Christophe Leroy wrote: > For SEC 2.x+, cipher in length must contain only the ciphertext length. turns out this should be 3.x+ > In case of using hardware ICV checking, the ICV length is provided via > the "extent" field of the descriptor pointer. > > Cc:

Re: [PATCH v1] mm: help the ALLOC_HARDER allocation pass the watermarki when CMA on

On Fri 23-03-18 15:57:32, Zhaoyang Huang wrote: > For the type of 'ALLOC_HARDER' page allocation, there is an express > highway for the whole process which lead the allocation reach __rmqueue_xxx > easier than other type. > However, when CMA is enabled, the free_page within zone_watermark_ok()

Re: linux-next: please clean up the alpine tree

Hi Stephen, On Fri, Mar 23, 2018 at 08:33:15AM +1100, Stephen Rothwell wrote: > > The alpine tree > (git://git.kernel.org/pub/scm/linux/kernel/git/atenart/linux.git#alpine/for-next) > only contains commits that have been upstreamed as different commits. > It also hasn't been updated since late

Re: [PATCH 4/8] clk: davinci: add a reset lookup table for psc0

2018-03-21 17:17 GMT+01:00 David Lechner : > On 03/21/2018 11:08 AM, Bartosz Golaszewski wrote: >> >> 2018-03-21 17:01 GMT+01:00 David Lechner : >>> >>> On 03/21/2018 07:08 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski

Re: [PATCH] memcg, thp: do not invoke oom killer on thp charges

On Thu 22-03-18 13:29:37, David Rientjes wrote: > On Thu, 22 Mar 2018, Michal Hocko wrote: [...] > > They simply cannot because kmalloc performs the change under the cover. > > So you would have to use kmalloc(gfp|__GFP_NORETRY) to be absolutely > > sure to not trigger _any_ oom killer. This is

Re: [REGRESSION v4.16-rc6] [PATCH] mqueue: forbid unprivileged user access to internal mount

Aleksa Sarai writes: > Hi all, > > Felix reported weird behaviour on 4.16.0-rc6 with regards to mqueue[1], > which was introduced by 36735a6a2b5e ("mqueue: switch to on-demand > creation of internal mount"). > > Basically, the reproducer boils down to being able to mount mqueue

Re: [v2] staging:fsl-mc: Move DPIO from staging to drivers/soc/fsl

: https://github.com/0day-ci/linux/commits/Roy-Pledge/staging-fsl-mc-Move-DPIO-from-staging-to-drivers-soc-fsl/20180323-102325 config: arm-allmodconfig (attached as .config) compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0 reproduce: wget https://raw.githubusercontent.com/intel/lkp

[PATCH] perf/x86/intel: fix linear IP of PEBS real_ip

this patch fix a bug in how the pebs->real_ip is handled in the PEBS handler. real_ip only exists in Haswell and later processor. It is actually the eventing ip, i.e., where the event occurred. As opposed to the pebs->ip which is the PEBS interrupt IP which is always off by one. The problem is

git send-email and sending the cover-letter to all cc addresses found in a patch series

On Thu, Mar 22, 2018 at 10:44:54AM -0700, Linus Torvalds wrote: > On Thu, Mar 22, 2018 at 10:29 AM, Peter Zijlstra wrote: > > > > But why !? Either Cc me on more of the series such that the whole makes > > sense, or better yet, write a proper Changelog. > > This is a common

Re: [RFC PATCH] nvme: avoid race-conditions when enabling devices

- Mail original - > De: "Marta Rybczynska" > À: "Keith Busch" > Cc: "Ming Lei" , ax...@fb.com, h...@lst.de, > s...@grimberg.me, linux-n...@lists.infradead.org, > linux-kernel@vger.kernel.org, bhelg...@google.com,

Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

On Fri, Mar 23, 2018 at 03:39:47AM +, Chris Packham wrote: > On 07/12/17 23:42, Wolfram Sang wrote: > > On Sun, Oct 29, 2017 at 06:29:18PM +0100, Wolfram Sang wrote: > >> On Wed, Jul 05, 2017 at 10:13:54PM +1200, Chris Packham wrote: > >>> This series addresses some of the points identified by

Re: git send-email and sending the cover-letter to all cc addresses found in a patch series

On Fri, 2018-03-23 at 08:38 +0100, Dominik Brodowski wrote: > On Thu, Mar 22, 2018 at 10:44:54AM -0700, Linus Torvalds wrote: > > On Thu, Mar 22, 2018 at 10:29 AM, Peter Zijlstra > > wrote: > > > > > > But why !? Either Cc me on more of the series such that the whole makes

Re: linux-next: build warning after merge of the tip tree

On Fri, Mar 23, 2018 at 01:28:53PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > lib/swiotlb.c:748:13: warning: 'swiotlb_free_buffer' defined but not used > [-Wunused-function] > static

Re: [PATCH 0/2] Kexec_file: Load kernel at top of system ram

On 03/22/18 at 03:38pm, Andrew Morton wrote: > On Thu, 22 Mar 2018 11:37:20 +0800 Baoquan He wrote: > > > The current kexec_file ignores kexec_buf.top_down value when call > > arch_kexec_walk_mem() to allocate memory for loading kernel/initrd > > stuffs. This is not supposed to

Re: [PATCH v3 1/1] can: ucan: add driver for Theobroma Systems UCAN devices

Am 22.03.2018 um 14:53 schrieb Jakob Unterwurzacher: > The UCAN driver supports the microcontroller-based USB/CAN > adapters from Theobroma Systems. There are two form-factors > that run essentially the same firmware: > > * Seal: standalone USB stick ( https://www.theobroma-systems.com/seal ) >

RE: [RFC PATCH] nvme: avoid race-conditions when enabling devices

Hi Marta, I could not get time to work on this. The present patch works for our platforms. so we continue with that. I will update new changes little later. If you have time, please try the same patch and let us know if any issue you see. Regards, Srinath. -Original Message- From: Marta

Re: [PATCH v2] cpuidle: poll_state: Add time limit to poll_idle()

On Fri, Mar 23, 2018 at 4:19 AM, Doug Smythies wrote: > On 2018.03.22 12:12 Doug Smythies wrote: >>On 2018.03.22 09:32 Rik van Riel wrote: >>> On Wed, 2018-03-14 at 13:04 +0100, Peter Zijlstra wrote: >>> On x86 we don't have to use that time_check_counter thing,

RE: [PATCH v5 7/7] iommu/dma: Move PCI window region reservation back into dma specific path.

> -Original Message- > From: Robin Murphy [mailto:robin.mur...@arm.com] > Sent: Thursday, March 22, 2018 5:22 PM > To: Alex Williamson ; Shameerali Kolothum > Thodi > Cc: eric.au...@redhat.com; pmo...@linux.vnet.ibm.com;

Re: [PATCH 03/10] mm: Assign memcg-aware shrinkers bitmap to memcg

-ci/linux/commits/Kirill-Tkhai/Improve-shrink_slab-scalability-old-complexity-was-O-n-2-new-is-O-n/20180323-052754 base: git://git.cmpxchg.org/linux-mmotm.git master reproduce: # apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__ sparse

[PATCH v1] mm: help the ALLOC_HARDER allocation pass the watermarki when CMA on

For the type of 'ALLOC_HARDER' page allocation, there is an express highway for the whole process which lead the allocation reach __rmqueue_xxx easier than other type. However, when CMA is enabled, the free_page within zone_watermark_ok() will be deducted for number the pages in CMA type, which

[PATCH net-next 0/2] kernel: add support to collect hardware logs in crash recovery kernel

On production servers running variety of workloads over time, kernel panic can happen sporadically after days or even months. It is important to collect as much debug logs as possible to root cause and fix the problem, that may not be easy to reproduce. Snapshot of underlying hardware/firmware

[PATCH net-next 2/2] cxgb4: collect hardware dump in second kernel

Register callback to collect hardware/firmware dumps in second kernel before hardware/firmware is initialized. The dumps for each device will be available under /sys/kernel/crashdd/cxgb4/ directory in second kernel. Signed-off-by: Rahul Lakkireddy Signed-off-by:

Re: [PATCH 1/2] bpf: Remove struct bpf_verifier_env argument from print_bpf_insn

On Thu, Mar 22, 2018 at 05:07:48PM +0100, Daniel Borkmann wrote: SNIP > >>> + va_end(args); > >>> +} > >>> EXPORT_SYMBOL_GPL(bpf_verifier_log_write); > >>> + > >>> +__printf(2, 3) static void print_ins(void *private_data, > >>> + const char *fmt, ...) > >> > >>

[PATCH v1 08/16] rtc: mediatek: remove unnecessary irq_dispose_mapping

From: Sean Wang It's unnecessary doing irq_dispose_mapping as a reverse operation for platform_get_irq. Ususally, irq_dispose_mapping should be called in error path or module removal to release the resources for irq_of_parse_and_map requested. Signed-off-by: Sean Wang

[PATCH v2 5/8] remoteproc: da8xx: add the missing retval check for clk_enable()

From: Bartosz Golaszewski The davinci platform is being switched to using the common clock framework, where clk_enable() can fail. Add the return value check. Signed-off-by: Bartosz Golaszewski --- drivers/remoteproc/da8xx_remoteproc.c | 8

[PATCH v2 1/8] reset: modify the way reset lookup works for board files

From: Bartosz Golaszewski Commit 7af1bb19f1d7 ("reset: add support for non-DT systems") introduced reset control lookup mechanism for boards that still use board files. The routine used to register lookup entries takes the corresponding reset_controlled_dev structure

Re: [PATCH 02/19] powerpc/powermac: Mark variable x as unused

Le 22/03/2018 à 21:19, Mathieu Malaterre a écrit : Since the value of x is never intended to be read, declare it with gcc attribute as unused. Fix warning treated as error with W=1: arch/powerpc/platforms/powermac/udbg_scc.c:76:9: error: variable ‘x’ set but not used

[PATCH v2 2/8] ARM: davinci: dts: make psc0 a reset provider

From: Bartosz Golaszewski The psc driver registers with the reset framework as a provider. Add the #reset-cells property to the psc0 node. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/da850.dtsi | 1 + 1 file changed, 1

Return checks for clock calls

Hi Shawn, Fabio, I'm trying to get the imx clks changes upstreamed. To that end, I reached this old commit that adds some wrappers over the generic clk API. Here is the commit message: ARM: imx6: add return check for clock calls There are a bunch of clk_enable_prepare,

[PATCH 4.15 09/84] net: fec: add phy_reset_after_clk_enable() support

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Richard Leitner [ Upstream commit 1b0a83ac04e383e3bed21332962b90710fcf2828 ] Some PHYs (for example the SMSC LAN8710/LAN8720) doesn't allow turning the refclk on

[PATCH 4.15 08/84] drm/msm: fix leak in failed get_pages

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Prakash Kamliya [ Upstream commit 62e3a3e342af3c313ab38603811ecdb1fcc79edb ] get_pages doesn't keep a reference of the pages allocated when it fails later in the

[PATCH 4.15 12/84] hv_netvsc: Fix the receive buffer size limit

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Haiyang Zhang [ Upstream commit 11b2b653102571ac791885324371d9a1a17b900e ] The max should be 31 MB on host with NVSP version > 2. On legacy hosts (NVSP version <=2)

[PATCH 4.15 02/84] staging: android: ashmem: Fix possible deadlock in ashmem_ioctl

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Yisheng Xie commit 740a5759bf222332fbb5eda42f89aa25ba38f9b2 upstream. ashmem_mutex may create a chain of dependencies like: CPU0

[PATCH 4.15 05/84] Bluetooth: btqcomsmd: Fix skb double free corruption

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Loic Poulain [ Upstream commit 67b8fbead4685b36d290a0ef91c6ddffc4920ec9 ] In case of hci send frame failure, skb is still owned by the caller (hci_core) and then

[PATCH 4.15 13/84] hv_netvsc: Fix the TX/RX buffer default sizes

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Haiyang Zhang [ Upstream commit 41f61db2cd24d5ad802386719cccde1479aa82a6 ] The values were not computed correctly. There are no significant visible impact, though.

[PATCH 4.15 44/84] PCI/ASPM: Calculate LTR_L1.2_THRESHOLD from device characteristics

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas [ Upstream commit 80d7d7a904fac3f8114448dbb8cc9fa253b10120 ] Per PCIe r3.1, sec 5.5.1, LTR_L1.2_THRESHOLD determines whether we enter the L1.2 Link state:

[PATCH 4.15 19/84] media: bt8xx: Fix err bt878_probe()

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit 45392ff6881dbe56d41ef0b17c2e576065f8ffa1 ] This is odd to call 'pci_disable_device()' in an error path before a

  1   2   3   4   5   6   7   8   9   10   >