Re: [PATCH v2 0/4] drm/tinydrm: new dirver for ILI9341 displays

"dirver"?

Re: [PATCH v2 3/4] dt-bindings: new binding for Ilitek ILI9341 display panels

On 05/25/2018 02:36 PM, David Lechner wrote: This adds a new binding for Ilitek ILI9341 display panels. It includes a compatible string for one display (more can be added in the future). The vendor prefix "noname" is used because the vendor is not known. Looks like I forgot to update "noname"

Re: [PATCH] xfs: mark sb_fname as nonstring

On Fri, May 25, 2018 at 6:52 PM, Christoph Hellwig wrote: >> diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c >> index 84fbf164cbc3..eb79f2bc4dcc 100644 >> --- a/fs/xfs/xfs_ioctl.c >> +++ b/fs/xfs/xfs_ioctl.c >> @@ -1819,12 +1819,12 @@ xfs_ioc_getlabel( >>

Re: [PATCH net-next] tcp: use data length instead of skb->len in tcp_probe

From: Song Liu Date: Thu, 24 May 2018 17:44:46 + > We should also rename __entry->length to __entry->data_len, so that whoever > using this field will notice the change. Agreed.

[PATCH 03/11] PM / devfreq: Remove check for df->max_freq == 0 from governors

Commit "PM / devfreq: Fix handling of min/max_freq == 0" ensures that df->max_freq is not 0, remove unnecessary checks. Signed-off-by: Matthias Kaehlcke --- drivers/devfreq/governor_performance.c| 5 + drivers/devfreq/governor_simpleondemand.c | 7 +++ 2 files

[PATCH 02/11] PM / devfreq: Fix handling of min/max_freq == 0

Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding the devfreq device") initializes df->min/max_freq with the min/max OPP when the device is added. Later commit f1d981eaecf8 ("PM / devfreq: Use the available min/max frequency") adds df->scaling_min/max_freq and the following to the

[PATCH 00/11] Add throttler driver for non-thermal throttling

This series adds the throttler driver, for non-thermal throttling of CPUs and devfreq devices. A use case for non-thermal throttling could be the detection of a high battery discharge voltage, close to the over-current protection (OCP) limit of the battery. To support throttling of devfreq

[PATCH 01/11] PM / devfreq: Init user limits from OPP limits, not viceversa

Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding the devfreq device") introduced the initialization of the user limits min/max_freq from the lowest/highest available OPPs. Later commit f1d981eaecf8 ("PM / devfreq: Use the available min/max frequency") added scaling_min/max_freq,

[PATCH 04/11] PM / devfreq: Remove redundant frequency adjustment from governors

The userspace and simpleondemand governor determine a target frequency and then adjust it according to the df->min/max_freq limits that might have been set by user space. This adjustment is redundant, it is done in update_devfreq() for any governor, right after returning from

Re: [PATCH net-next] ifb: fix packets checksum

From: Jon Maxwell Date: Fri, 25 May 2018 07:38:29 +1000 > Fixup the checksum for CHECKSUM_COMPLETE when pulling skbs on RX path. > Otherwise we get splats when tc mirred is used to redirect packets to ifb. > > Before fix: > > nic: hw csum failure > > Signed-off-by: Jon

Re: [PATCH v4 2/3] media: rc: introduce BPF_PROG_LIRC_MODE2

On Fri, May 18, 2018 at 03:07:29PM +0100, Sean Young wrote: > Add support for BPF_PROG_LIRC_MODE2. This type of BPF program can call > rc_keydown() to reported decoded IR scancodes, or rc_repeat() to report > that the last key should be repeated. > > The bpf program can be attached to using the

Re: [patch] mm, hugetlb_cgroup: suppress SIGBUS when hugetlb_cgroup charge fails

On Fri, 25 May 2018 13:16:45 -0700 (PDT) David Rientjes wrote: > When charging to a hugetlb_cgroup fails, alloc_huge_page() returns > ERR_PTR(-ENOSPC) which will cause VM_FAULT_SIGBUS to be returned to the > page fault handler. > > Instead, return the proper error code,

Re: [PATCH] mm, page_alloc: do not break __GFP_THISNODE by zonelist reset

On 05/25/2018 09:43 PM, Andrew Morton wrote: > On Fri, 25 May 2018 15:08:53 +0200 Vlastimil Babka wrote: > >> we might consider this for 4.17 although I don't know if there's anything >> currently broken. Stable backports should be more important, but will have to >> be reviewed

Re: [clang] stack protector and f1f029c7bf

On 05/25/18 13:36, Nick Desaulniers wrote: > On Fri, May 25, 2018 at 10:56 AM wrote: >> You need the extern inline in the .h file and the out-of-line .S file > both. > > But the out-of-line .S file looks like: > > ... > 10 ENTRY(native_save_fl) > > 11 pushf > >

Re: [PATCH v3 13/14] tracing/selftest: Add selftests to test trace_marker histogram triggers

On Fri, 25 May 2018 17:12:29 -0400 Steven Rostedt wrote: > #!/bin/sh Hmm, I think I need to make this #!/bin/bash > test_trace() { > file=$1 > x=$2 > > cat $file | while read line; do > if [ "$line" != "${line/\#/}" ]; then > continue >

[PATCH v5 04/10] sched/dl: add dl_rq utilization tracking

Similarly to what happens with rt tasks, cfs tasks can be preempted by dl tasks and the cfs's utilization might no longer describes the real utilization level. Current dl bandwidth reflects the requirements to meet deadline when tasks are enqueued but not the current utilization of the dl sched

Re: [PATCH] ath6kl: mark expected switch fall-throughs

Sergei Shtylyov writes: > On 5/25/2018 2:13 AM, Gustavo A. R. Silva wrote: > >> In preparation to enabling -Wimplicit-fallthrough, mark switch cases >> where we are expecting to fall through. >> >> Signed-off-by: Gustavo A. R. Silva >>

Re: [PATCH V2] PCI/portdrv: do not disable device on reboot/shutdown

On 5/24/2018 2:35 PM, Bjorn Helgaas wrote: > That sounds like a reasonable idea, and it is definitely another can > of worms. I looked briefly at some of the .shutdown() cases: should we throw it into 4.18 and see what happens? -- Sinan Kaya Qualcomm Datacenter Technologies, Inc. as an

Re: [PATCH] PCI: hv: Do not wait forever on a device that has disappeared

On Wed, May 23, 2018 at 09:12:01PM +, Dexuan Cui wrote: > > Before the guest finishes the device initialization, the device can be > removed anytime by the host, and after that the host won't respond to > the guest's request, so the guest should be prepared to handle this > case. > >

Re: [PATCH v3 6/6] tty/serial: atmel: changed the driver to work under at91-usart mfd

On 05/25/2018 04:35 PM, Richard Genoud wrote: On 25/05/2018 14:17, Radu Pirea wrote: On 05/15/2018 04:14 PM, Richard Genoud wrote: On 15/05/2018 14:47, Radu Pirea wrote: On Mon, 2018-05-14 at 12:57 +0200, Richard Genoud wrote: After your patch, the DMA is not selected anymore:

Re: [PATCH 0/3] Provide more fine grained control over multipathing

On Fri, May 25, 2018 at 09:58:13AM -0400, Mike Snitzer wrote: > We all basically knew this would be your position. But at this year's > LSF we pretty quickly reached consensus that we do in fact need this. > Except for yourself, Sagi and afaik Martin George: all on the cc were in > attendance and

Re: [PATCH v2 1/2] rcu: Update documentation of rcu_read_unlock()

On Fri, May 25, 2018 at 11:05:06AM +0200, Anna-Maria Gleixner wrote: > Since commit b4abf91047cf ("rtmutex: Make wait_lock irq safe") the > explanation in rcu_read_unlock() documentation about irq unsafe rtmutex > wait_lock is no longer valid. > > Remove it to prevent kernel developers reading

Re: [PATCH v5 01/10] sched/pelt: Move pelt related code in a dedicated file

Hi Vincent, On Friday 25 May 2018 at 15:12:22 (+0200), Vincent Guittot wrote: > We want to track rt_rq's utilization as a part of the estimation of the > whole rq's utilization. This is necessary because rt tasks can steal > utilization to cfs tasks and make them lighter than they are. > As we

[PATCH v3 0/8] slimbus: fixes and some helpers

Hi Greg, Here is set of patches for slimbus, there are 6 fixes and two helper functions. Most of these issues were found while testing QCOM NGD SLIMBus controller with WCD9335 codec. Changes since v2 (https://lkml.org/lkml/2018/5/17/251) - removed unnecessary changes in slim_prepare_txn patch

[PATCH v3 3/8] slimbus: messaging: pass correct wbuf

There seems to be a typo while filling msg for slim_write, wbuf is set to NULL instead of rbuf. Signed-off-by: Srinivas Kandagatla --- drivers/slimbus/messaging.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/slimbus/messaging.c

[PATCH v3 1/8] slimbus: core: rearrange slim_eaddr structure

Rearrange struct slim_eaddr so that the structure is packed correctly to be able to send in SLIMBus messages. Signed-off-by: Srinivas Kandagatla --- include/linux/slimbus.h | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git

[PATCH] xfs: mark sb_fname as nonstring

gcc-8 reports two warnings for the newly added getlabel/setlabel code: fs/xfs/xfs_ioctl.c: In function 'xfs_ioc_getlabel': fs/xfs/xfs_ioctl.c:1822:38: error: argument to 'sizeof' in 'strncpy' call is the same expression as the source; did you mean to use the size of the destination?

[PATCH 4/5] media: marvel-ccic: allow ccic and mmp drivers to coexist

Randconfig builds fail when one of the two is a built-in driver and the other one is a loadable module: drivers/media/platform/marvell-ccic/mcam-core.o: In function `mccic_register': mcam-core.c:(.text+0x2594): undefined reference to `__this_module'

[PATCH 5/5] media: omap2: fix compile-testing with FB_OMAP2=m

Compile-testing with FB_OMAP2=m results in a link error: drivers/media/platform/omap/omap_vout.o: In function `vidioc_streamoff': omap_vout.c:(.text+0x1028): undefined reference to `omap_dispc_unregister_isr' drivers/media/platform/omap/omap_vout.o: In function `omap_vout_release':

[PATCH 3/5] media: cx231xx: fix RC_CORE dependency

With CONFIG_RC_CORE=m and VIDEO_CX231XX=y, we get a link failure: drivers/media/usb/cx231xx/cx231xx-input.o: In function `cx231xx_ir_init': cx231xx-input.c:(.text+0xd4): undefined reference to `rc_allocate_device' This narrows down the dependency so that only valid configurations are allowed.

[PATCH 2/5] media: v4l: cadence: include linux/slab.h

I ran into a randconfig build error with the new driver: drivers/media/platform/cadence/cdns-csi2tx.c: In function 'csi2tx_probe': drivers/media/platform/cadence/cdns-csi2tx.c:477:11: error: implicit declaration of function 'kzalloc'; did you mean 'd_alloc'?

[PATCH] HID: steam: select CONFIG_POWER_SUPPLY

Using the power supply APIs requires selecting the appropriate Kconfig symbol, otherwise we get this build failure: drivers/hid/hid-steam.o: In function `steam_unregister': hid-steam.c:(.text+0x1cc): undefined reference to `power_supply_unregister' drivers/hid/hid-steam.o: In function

Re: [PATCH -V2 -mm 0/4] mm, huge page: Copy target sub-page last when copy huge page

On Thu, 24 May 2018, Huang, Ying wrote: > If the cache contention is heavy when copying the huge page, and we > copy the huge page from the begin to the end, it is possible that the > begin of huge page is evicted from the cache after we finishing > copying the end of the huge page. And it is

Re: [PATCH] remoteproc: Add APSS based Qualcomm ADSP PIL driver for SDM845

On Thu, May 24, 2018 at 12:18 AM, Rohit Kumar wrote: > Thanks Bjorn for reviewing. > > > On 5/23/2018 11:56 AM, Bjorn Andersson wrote: >> >> On Sun 13 May 00:01 PDT 2018, Rohit kumar wrote: >> >> [..] >>> >>> +static inline void update_bits(void *reg, u32 mask_val, u32

Re: [PATCH 08/11] coresight: Add generic TMC sg table framework

On 23/05/18 21:25, Mathieu Poirier wrote: On Fri, May 18, 2018 at 05:39:24PM +0100, Suzuki K Poulose wrote: This patch introduces a generic sg table data structure and associated operations. An SG table can be used to map a set of Data pages where the trace data could be stored by the TMC ETR.

Re: [GIT PULL] PHY: for 4.18

On Tue, May 22, 2018 at 06:08:18AM +0530, Kishon Vijay Abraham I wrote: > Hi Greg, > > Please find the pull request for 4.18 merge window below. It adds a couple of > new USB PHY drivers, adds support for couple of newer PHYs in existing > drivers and few cleanups. Please find the complete set of

Re: [PATCH v6 0/3] driver-core: return EINVAL error instead of BUG_ON()

On Wed, May 23, 2018 at 05:59:10PM +0200, Florian Schmaus wrote: > This patch series makes driver_register() emit an error message and > return a failure code instead of triggering a BUG_ON(). > > The first patch will cause driver_register() to fail gracefully if the > driver's bus was not

Re: [PATCH 08/11] coresight: Add generic TMC sg table framework

On Fri, May 25, 2018 at 05:07:07PM +0100, Suzuki K Poulose wrote: > On 23/05/18 21:25, Mathieu Poirier wrote: > >On Fri, May 18, 2018 at 05:39:24PM +0100, Suzuki K Poulose wrote: > >>This patch introduces a generic sg table data structure and > >>associated operations. An SG table can be used to

Re: [PATCH] xfs: mark sb_fname as nonstring

On 5/25/18 10:14 AM, Arnd Bergmann wrote: gcc-8 reports two warnings for the newly added getlabel/setlabel code: Thanks for catching these. The patch summary confuses me, what does "mark sb_fname as nonstring" mean in the context of the actual patch? I hate strings in C! ;)

[PATCH v3 3/6] arm64: untag user addresses in access_ok and __uaccess_mask_ptr

copy_from_user (and a few other similar functions) are used to copy data from user memory into the kernel memory or vice versa. Since a user can provided a tagged pointer to one of the syscalls that use copy_from_user, we need to correctly handle such pointers. Do this by untagging user pointers

[PATCH v3 6/6] arm64: update Documentation/arm64/tagged-pointers.txt

Add a note that work on passing tagged user pointers to the kernel via syscalls has started, but might not be complete yet. Signed-off-by: Andrey Konovalov --- Documentation/arm64/tagged-pointers.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

[PATCH v3 0/6] arm64: untag user pointers passed to the kernel

arm64 has a feature called Top Byte Ignore, which allows to embed pointer tags into the top byte of each pointer. Userspace programs (such as HWASan, a memory debugging tool [1]) might use this feature and pass tagged user pointers to the kernel through syscalls or other interfaces. This patch

Re: [PATCH 6/6] coresight: allow to build as modules

On 24 May 2018 at 17:49, Kim Phillips wrote: > On Tue, 22 May 2018 15:39:06 -0600 > Mathieu Poirier wrote: > >> On Thu, May 17, 2018 at 08:20:24PM -0500, Kim Phillips wrote: >> > Allow to build coresight as modules. This greatly enhances

[PATCH v3 5/6] lib, arm64: untag addrs passed to strncpy_from_user and strnlen_user

strncpy_from_user and strnlen_user accept user addresses as arguments, and do not go through the same path as copy_from_user and others, so here we need to handle the case of tagged user addresses separately. Untag user pointers passed to these functions. Signed-off-by: Andrey Konovalov

[PATCH] atm: zatm: fix memcmp casting

memcmp() returns int, but eprom_try_esi() cast it to unsigned char. One can lose significant bits and get 0 from non-0 value returned by the memcmp(). Signed-off-by: Ivan Bornyakov --- drivers/atm/zatm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [clang] stack protector and f1f029c7bf

On Fri, May 25, 2018 at 10:35 AM Tom Stellard wrote: > On 05/25/2018 10:31 AM, Nick Desaulniers wrote: > > On Fri, May 25, 2018 at 9:53 AM wrote: > >> On May 25, 2018 9:46:42 AM PDT, Nick Desaulniers < ndesaulni...@google.com> > > wrote: > >>> On Fri, May 25,

Re: [PATCH v3 13/14] tracing/selftest: Add selftests to test trace_marker histogram triggers

On Wed, 23 May 2018 23:13:31 +0900 Masami Hiramatsu wrote: > This looks good to me. > > Acked-by: Masami Hiramatsu Thanks! > > BTW, would you plan to add simplar test case for the marker? > (like just write a marker and read trace log, and run a

Re: [PATCH] ath6kl: mark expected switch fall-throughs

"Gustavo A. R. Silva" writes: > On 05/25/2018 08:30 AM, Kalle Valo wrote: >> Sergei Shtylyov writes: >> >>> On 5/25/2018 2:13 AM, Gustavo A. R. Silva wrote: >>> In preparation to enabling -Wimplicit-fallthrough, mark switch cases

Re: [PATCH] arm64: dts: qcom: msm8996: Use UFS_GDSC for UFS

On Fri 25 May 05:51 PDT 2018, Vivek Gautam wrote: > Hi Bjorn, > > On Fri, May 25, 2018 at 4:01 AM, Bjorn Andersson > wrote: > > The UFS host controller occationally (20%) fails to enable > > gcc_ufs_axi_clk because the UFS GDSC is not enabled. In most cases it's > >

[PATCH net-next 05/12] net: hns3: Fix for PF mailbox receving unknown message

From: Xi Wang Before the firmware updates the crq's tail pointer, if the PF driver reads the data in the crq, the data may be incomplete at this time, which will lead to the driver read an unknown message. This patch fixes it by checking if crq is not empty before reading

[PATCH net-next 04/12] net: hns3: Add support to enable TX/RX promisc mode for H/W rev(0x21)

From: Peng Li HCLGE_PROMISC_TX_EN_B and HCLGE_PROMISC_RX_EN_B are not supported on pdev revision(0x20), new revision(0x21) supports them. Signed-off-by: Peng Li Signed-off-by: Salil Mehta ---

[PATCH net-next 07/12] net: hns3: Fixes the init of the VALID BD info in the descriptor

From: Fuyun Liang RX Buffer Descriptor contains a VALID bit which indicates if the BD is valid and has some data. This field is set by HNS3 hardware to intimate the driver of some valid data present in the BD. nd should be reset by the driver when BD is being used again.

[PATCH net-next 00/12] Misc. bug fixes & some minor additions to HNS3 driver

This patch-set provides some bug fixes figured out during testing and review. It also provides some additions due to running of the existing code on the new revision of the HNS3 hardware. Fuyun Liang (3): net: hns3: Fixes the init of the VALID BD info in the descriptor net: hns3: Removes

Re: [PATCH net-next] net: fec: remove stale comment

From: YueHaibing Date: Thu, 24 May 2018 19:27:07 +0800 > This comment is outdated as fec_ptp_ioctl has been replaced by > fec_ptp_set/fec_ptp_get > since commit 1d5244d0e43b ("fec: Implement the SIOCGHWTSTAMP ioctl") > > Signed-off-by: YueHaibing

Re: [PATCH 1/6] coresight: remove CORESIGHT_LINKS_AND_SINKS dependencies and selections

On 25 May 2018 at 12:52, Kim Phillips wrote: > On Fri, 25 May 2018 09:27:09 -0600 > Mathieu Poirier wrote: > >> On 24 May 2018 at 17:30, Kim Phillips wrote: >> > On Thu, 24 May 2018 09:32:48 -0600 >> > Mathieu Poirier

[PATCH] PCI: qcom: Fix error handling in pm_runtime support

The driver does not cope with the fact that probe can fail in a number of cases after enabling pm_runtime on the device, this results in warnings about "Unbalanced pm_runtime_enable". Further more if probe fails after invoking host_init the power-domain will be left referenced. As it's not

Re: [clang] stack protector and f1f029c7bf

On May 25, 2018 9:46:42 AM PDT, Nick Desaulniers wrote: >On Fri, May 25, 2018 at 9:33 AM wrote: >> On May 25, 2018 9:27:40 AM PDT, Nick Desaulniers > >wrote: >> >On Thu, May 24, 2018 at 3:43 PM wrote: >> >> On

Re: [PATCH 08/11] coresight: Add generic TMC sg table framework

On 25/05/18 17:43, Mathieu Poirier wrote: On Fri, May 25, 2018 at 05:07:07PM +0100, Suzuki K Poulose wrote: On 23/05/18 21:25, Mathieu Poirier wrote: On Fri, May 18, 2018 at 05:39:24PM +0100, Suzuki K Poulose wrote: This patch introduces a generic sg table data structure and associated

Re: [PATCH 4/8] drm/rcar-du: fix merge conflict for state->alpha

Hi Arnd, Thank you for the patch. On Friday, 25 May 2018 18:50:11 EEST Arnd Bergmann wrote: > The "alpha" struct member was removed in one commit but another user > added in another, leading to a build failure: > > drivers/gpu/drm/rcar-du/rcar_du_vsp.c: In function >

[PATCH v3 4/6] mm, arm64: untag user addresses in mm/gup.c

mm/gup.c provides a kernel interface that accepts user addresses and manipulates user pages directly (for example get_user_pages, that is used by the futex syscall). Here we also need to handle the case of tagged user pointers. Add untagging to gup.c functions that use user pointers for vma

[PATCH v3 1/6] arm64: add type casts to untagged_addr macro

This patch makes the untagged_addr macro accept all kinds of address types (void *, unsigned long, etc.) and allows not to specify type casts in each place where it is used. This is done by using __typeof__. Signed-off-by: Andrey Konovalov ---

linux-next: Tree for May 24

Hi all, This tree is being released on the 25th but it's actually a snapshot from the 24th that I started building on the 24th but didn't go as quickly as hoped, sorry. There should be another linux-next done by me for today (25th) as well, that will appear tomorrow all being well. Stephen

Re: [clang] stack protector and f1f029c7bf

On Fri, May 25, 2018 at 9:53 AM wrote: > On May 25, 2018 9:46:42 AM PDT, Nick Desaulniers wrote: > >On Fri, May 25, 2018 at 9:33 AM wrote: > >> On May 25, 2018 9:27:40 AM PDT, Nick Desaulniers > > wrote: > >When

[PATCH] x86/spectre_v1: Disable compiler optimizations over array_index_mask_nospec()

Mark notes that gcc optimization passes have the potential to elide necessary invocations of this instruction sequence, so include an optimization barrier. > I think that either way, we have a potential problem if the compiler > generates a branch dependent on the result of

Applied "ASoC: omap: fix compile-test building" to the asoc tree

The patch ASoC: omap: fix compile-test building has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Re: [RFC V2] virtio: Add platform specific DMA API translation for virito devices

On Thu, May 24, 2018 at 08:27:04AM +1000, Benjamin Herrenschmidt wrote: > On Wed, 2018-05-23 at 21:50 +0300, Michael S. Tsirkin wrote: > > > I re-read that discussion and I'm still unclear on the > > original question, since I got several apparently > > conflicting answers. > > > > I asked: > >

Re: [clang] stack protector and f1f029c7bf

On Fri, May 25, 2018 at 10:49 AM Nick Desaulniers wrote: > gcc 8.1 and trunk inserts a `ud2` instruction (what?!) (let me see if I can > repro outside of godbolt, and will file a bug report). Filed: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85927 -- Thanks, ~Nick

Re: [PATCH] tools/power/x86/intel_pstate_tracer: Add optional setting of trace buffer memory allocation

On Thu, 2018-05-24 at 11:34 +0200, Rafael J. Wysocki wrote: > On Sunday, May 13, 2018 10:43:02 AM CEST Rafael J. Wysocki wrote: > > On Friday, May 4, 2018 3:46:22 PM CEST Doug Smythies wrote: > > > Allow the user to override the default trace buffer memory > > > allocation > > > by adding a

[PATCH 6/9] clk: davinci: pll: allow dev == NULL

This modifies the TI Davinci PLL clock driver to allow for the case when dev == NULL. On some (most) SoCs that use this driver, the PLL clock needs to be registered during early boot because it is used for clocksource/clkevent and there will be no platform device available. Signed-off-by: David

Re: [PATCH] kernel: sys: fix potential Spectre v1

On 05/23/2018 11:31 AM, Mark Rutland wrote: On Wed, May 23, 2018 at 04:07:37PM +0100, Mark Rutland wrote: I think that either way, we have a potential problem if the compiler generates a branch dependent on the result of validate_index_nospec(). In that case, we could end up with codegen

[PATCH 3/9] clk: davinci: psc-dm355: fix ASP0/1 clkdev lookups

The clkdev lookups for the ASP0/1 devices on TI DM355 were declared, but not assigned to any LPSC. This assigns the clkdev lookups to the correct LPSCs. Reported-by: Sekhar Nori Signed-off-by: David Lechner Reviewed-by: Sekhar Nori ---

[PATCH 8/9] clk: davinci: psc: allow for dev == NULL

On some davinci SoCs, we need to register the PSC clocks during early boot because they are needed for clocksource/clockevent. These changes allow for dev == NULL because in this case, we won't have a platform device for the clocks. Signed-off-by: David Lechner Reviewed-by:

[PATCH v2] ath6kl: mark expected switch fall-throughs

In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. Signed-off-by: Gustavo A. R. Silva --- Changes in v2: - Place code comments on a line of their own. drivers/net/wireless/ath/ath6kl/cfg80211.c | 3 +++ 1 file

Re: [PATCH v2] ath6kl: mark expected switch fall-throughs

On Fri, May 25, 2018 at 11:23 AM Gustavo A. R. Silva wrote: > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > where we are expecting to fall through. > Signed-off-by: Gustavo A. R. Silva > --- > Changes in v2: >- Place

[PATCH] memcg: force charge kmem counter too

Based on several conditions the kernel can decide to force charge an allocation for a memcg i.e. overcharge memcg->memory and memcg->memsw counters. Do the same for memcg->kmem counter too. In cgroup-v1, this bug can cause a __GFP_NOFAIL kmem allocation fail if an explicit limit on kmem counter is

Re: [PATCH 2/2] ARM: shmobile: only call secure_cntvoff_init on SMP builds

Hi Arnd, On Fri, May 25, 2018 at 6:10 PM, Arnd Bergmann wrote: > The secure_cntvoff_init() function is not available without CONFIG_SMP, > leading to a link error on shmobile: > > arch/arm/mach-shmobile/setup-rcar-gen2.o: In function `rcar_gen2_timer_init': >

Re: [PATCH 4.4 00/92] 4.4.133-stable review

On Fri, May 25, 2018 at 09:39:19AM -0700, Guenter Roeck wrote: > On Fri, May 25, 2018 at 04:11:45PM +0200, Greg Kroah-Hartman wrote: > > On Thu, May 24, 2018 at 09:47:42PM +0200, Greg Kroah-Hartman wrote: > > > On Thu, May 24, 2018 at 10:32:08AM -0700, Guenter Roeck wrote: > > > > On Thu, May 24,

[PATCH v3 2/6] uaccess: add untagged_addr definition for other arches

To allow arm64 syscalls accept tagged pointers from userspace, we must untag them when they are passed to the kernel. Since untagging is done in generic parts of the kernel (like the mm subsystem), the untagged_addr macro should be defined for all architectures. Define it as a noop for other

Applied "regmap: slimbus: allow register offsets up to 16 bits" to the regmap tree

The patch regmap: slimbus: allow register offsets up to 16 bits has been applied to the regmap tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "regmap: add missing prototype for devm_init_slimbus" to the regmap tree

The patch regmap: add missing prototype for devm_init_slimbus has been applied to the regmap tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Re: [RFC PATCH net-next 00/12] XDP batching for TUN/vhost_net

On Mon, May 21, 2018 at 05:04:21PM +0800, Jason Wang wrote: > Hi all: > > We do not support XDP batching for TUN since it can only receive one > packet a time from vhost_net. This series tries to remove this > limitation by: > > - introduce a TUN specific msg_control that can hold a pointer to

Re: [clang] stack protector and f1f029c7bf

On May 25, 2018 10:49:28 AM PDT, Nick Desaulniers wrote: >On Fri, May 25, 2018 at 10:35 AM Tom Stellard >wrote: >> On 05/25/2018 10:31 AM, Nick Desaulniers wrote: >> > On Fri, May 25, 2018 at 9:53 AM wrote: >> >> On May 25, 2018

Re: [PATCH v3 14/14] tracing/selftest: Add test to test hist trigger between kernel event and trace_marker

On Wed, 23 May 2018 23:15:59 +0900 Masami Hiramatsu wrote: > On Wed, 16 May 2018 11:00:26 -0400 > Steven Rostedt wrote: > > > From: "Steven Rostedt (VMware)" > > > > Add a test that tests a trigger that is initiated by a kernel

Re: [PATCH v11 00/27] ARM: davinci: convert to common clock framework​

On 05/22/2018 04:38 AM, Sekhar Nori wrote: Hi David, On Friday 18 May 2018 10:18 PM, David Lechner wrote: This series converts mach-davinci to use the common clock framework. The series works like this, the first 3 patches fix some issues with the clock drivers that have already been accepted

[PATCH net-next 02/12] net: hns3: Add support for tx_accept_tag2 and tx_accept_untag2 config

From: Peng Li HNS3 Hardware can support up to two VLAN tags in transmit leg, the PPP module can handle the packets based on the tag1 and tag2 config. This patch adds support for tag2 config for vlan handling Signed-off-by: Peng Li Signed-off-by:

Re: [PATCH v2] ath6kl: mark expected switch fall-throughs

On 05/25/2018 01:27 PM, Steve deRosier wrote: On Fri, May 25, 2018 at 11:23 AM Gustavo A. R. Silva wrote: In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. Signed-off-by: Gustavo A. R. Silva

[PATCH RFC tools/memory-model] Add litmus-test naming scheme

This commit documents the scheme used to generate the names for the litmus tests. Signed-off-by: Paul E. McKenney --- README | 136 - 1 file changed, 135 insertions(+), 1 deletion(-) diff --git

[PATCH RFC rcu/x86] Provide early rcu_cpu_starting() callback

The x86/mtrr code does horrific things because hardware. It uses stop_machine_from_inactive_cpu(), which does a wakeup (of the stopper thread on another CPU), which uses RCU, all before the CPU is onlined. RCU complains about this, because wakeups use RCU and RCU does (rightfully) not consider

[PATCH] iommu/msm: Don't call iommu_device_{,un}link from atomic context

Fixes the following splat during boot: BUG: sleeping function called from invalid context at kernel/locking/mutex.c:747 in_atomic(): 1, irqs_disabled(): 128, pid: 77, name: kworker/2:1 4 locks held by kworker/2:1/77: #0: (ptrval) ((wq_completion)"events"){+.+.}, at: process_one_work+0x1fc/0x8fc

Re: [PATCH bpf-next v2 0/3] bpf: add boot parameters for sysctl knobs

On Thu, May 24, 2018 at 04:34:51PM -0700, Alexei Starovoitov wrote: > On Thu, May 24, 2018 at 09:41:08AM +0200, Jesper Dangaard Brouer wrote: > > On Wed, 23 May 2018 15:02:45 -0700 > > Alexei Starovoitov wrote: > > > > > On Wed, May 23, 2018 at 02:18:19PM +0200,

[PATCH v4 0/6] Driver for at91 usart in spi mode

Hello, This is the second version of driver. I added a mfd driver which by default probes atmel_serial driver and if in dt is specified to probe the spi driver, then the spi-at91-usart driver will be probed. The compatible for atmel_serial is now the compatible for at91-usart mfd driver and

[PATCH v4 3/6] mfd: at91-usart: added mfd driver for usart

This mfd driver is just a wrapper over atmel_serial driver and spi-at91-usart driver. Selection of one of the drivers is based on a property from device tree. If the property is not specified, the default driver is atmel_serial. Signed-off-by: Radu Pirea ---

[PATCH v4 2/6] dt-bindings: add binding for atmel-usart in SPI mode

This patch moves the bindings for serial from serial/atmel-usart.txt to mfd/atmel-usart.txt and adds bindings for USART in SPI mode. Signed-off-by: Radu Pirea --- .../bindings/{serial => mfd}/atmel-usart.txt | 25 +-- 1 file changed, 23 insertions(+),

[PATCH v4 1/6] MAINTAINERS: add at91 usart mfd driver

Added entry for at91 usart mfd driver. Signed-off-by: Radu Pirea --- MAINTAINERS | 9 + 1 file changed, 9 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 8e2a2fddbd19..12203d07c6af 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -9160,6 +9160,7 @@ M:

[PATCH v4 6/6] tty/serial: atmel: changed the driver to work under at91-usart mfd

This patch modifies the place where resources and device tree properties are searched. Signed-off-by: Radu Pirea --- drivers/tty/serial/Kconfig| 1 + drivers/tty/serial/atmel_serial.c | 40 +-- 2 files changed, 23 insertions(+), 18

[PATCH v4 5/6] spi: at91-usart: add driver for at91-usart as spi

This is the driver for at91-usart in spi mode. The USART IP can be configured to work in many modes and one of them is SPI. The driver was tested on sama5d3-xplained and sama5d4-xplained boards with enc28j60 ethernet controller as slave. Signed-off-by: Radu Pirea ---

[PATCH v4 4/6] MAINTAINERS: add at91 usart spi driver

Added entry for at91 usart mfd driver. Signed-off-by: Radu Pirea --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 12203d07c6af..dae31df711fb 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -9201,6 +9201,13 @@ F:

Re: [PATCH 6/6] coresight: allow to build as modules

On 25 May 2018 at 11:12, Suzuki K Poulose wrote: > On 18/05/18 02:20, Kim Phillips wrote: >> >> Allow to build coresight as modules. This greatly enhances developer >> efficiency by allowing the development to take place exclusively on the >> target, and without needing

Re: [alsa-devel] [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files

On Fri, May 25, 2018 at 7:09 AM Guenter Roeck wrote: > On Fri, May 25, 2018 at 6:42 AM Shreyas NC wrote: > > > > > +struct skl_dfw_v4_pipe { > > > > > + u8 pipe_id; > > > > > + u8 pipe_priority; > > > > > + u16 conn_type:4; > > > > > +

Re: [PATCH] ath6kl: mark expected switch fall-throughs

On 05/25/2018 08:30 AM, Kalle Valo wrote: Sergei Shtylyov writes: On 5/25/2018 2:13 AM, Gustavo A. R. Silva wrote: In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. Signed-off-by: Gustavo A. R.

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