Re: [RFC PATCH bpf-next v2 1/4] tracing/kprobe: bpf: Check error injectable event is on function entry

On Wed, 27 Dec 2017 20:32:07 -0800 Alexei Starovoitov wrote: > On 12/27/17 8:16 PM, Steven Rostedt wrote: > > On Wed, 27 Dec 2017 19:45:42 -0800 > > Alexei Starovoitov wrote: > > > >> I don't think that's the case. My reading of current > >> trace_kprobe_ftrace() ->

Re: [PATCH 0/4] KVM: nVMX: prepare_vmcs02 optimizations

2017-12-27 22:28 GMT+08:00 Paolo Bonzini : > On 25/12/2017 11:08, Wanpeng Li wrote: >>> I observe L1(latest kvm/queue) panic and L0(latest kvm/queue) >>> calltrace, I'm not sure whether it is caused by this patchset. >> It can be reproduced steadily by running kvm-unit-tests

Re: stable-rc build: 0 warnings 7 failures (stable-rc/v3.18.90-13-g444eb56)

On Thu, Dec 28, 2017 at 8:38 AM, Olof's autobuilder wrote: > Here are the build results from automated periodic testing. > > The tree being built was stable-rc, found at: > > URL: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > Branch: linux-3.18.y >

Re: [RFC PATCH v12 4/5] PCI / PM: Add support for the PCIe WAKE# signal for OF

On Wed, 2017-12-27 at 09:30 -0600, Rob Herring wrote: > On Tue, Dec 26, 2017 at 7:32 PM, JeffyChen > wrote: > this new file does something similar to the pci-acpi.c and pci-mid.c.. > pci-acpi.c has similar things to pci/of.c. The naming is just not > consistent. > >

Re: lost connection to test machine (3)

On Wed, Dec 27, 2017 at 10:36 PM, Florian Westphal wrote: > Dmitry Vyukov wrote: >> On Wed, Dec 27, 2017 at 7:18 PM, syzbot >> wrote: >> > Hello, >> > >> > syzkaller hit the following crash on >> >

Re: kernel panic: Attempted to kill init! (2)

On Thu, Dec 28, 2017 at 10:20 AM, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 6084b576dca2e898f5c101baef151f7bfdbb606d > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC)

4.14.9 with CONFIG_MCORE2 fails to boot

Hello, 4.14.9 fails to boot if CONFIG_MCORE2 is enabled and when compiled with gcc 6+. More details in the following bug reports: https://bugzilla.kernel.org/show_bug.cgi?id=198263 https://bugs.gentoo.org/642268 I bisected it to the commit below: $ git bisect good

[PATCH 1/3] mmc: sdhci: fix SDHCI_QUIRK2_CLEAR_TRANSFERMODE_REG_BEFORE_CMD handling

SD controller with SDHCI_QUIRK2_CLEAR_TRANSFERMODE_REG_BEFORE_CMD quirk will clear SD host transfer mode register for non-data commands. But in eMMC HS200 hardware tuning case, the hardware tuning process need to transfer mode register has properly value. So don't clear transfer mode register when

RE: [PATCH] PCI: imx6: Add PHY reference clock source support

Hi Ilya: I think the "ocsillator" in the binding document should be oscillator. Thanks. Best Regards Richard Best Regards hongxing zhu Linux BSP team Office: 86-21-28937189 Email: hongxing@nxp.com -Original Message- From: Ilya Ledvich [mailto:i...@compulab.co.il] Sent: Wednesday,

Re: [RFC][PATCHv6 00/12] printk: introduce printing kernel thread

On (12/28/17 15:48), Sergey Senozhatsky wrote: [..] > and I'm actually thinking about returning back the old vprintk_emit() > behavior > >vprintk_emit() >{ > + preempt_disable(); > if (console_trylock()) > console_unlock(); > +

Re: [PATCH v1] x86/platform/intel-mid: Revert "Make 'bt_sfi_data' const"

* Andy Shevchenko wrote: > The annoying static analyzer follow up patches make a pain rather then > fixing issues. > > The one done by commit 276c87054751 > > ("x86/platform/intel-mid: Make 'bt_sfi_data' const") > > made an obvious regression [BugLink]

Re: [PATCH v3] mtd: spi-nor: Add ISSI is25lp080d support

Le 28/12/2017 à 11:03, Romain Porte a écrit : > Add support for a new ISSI 1MB SPI NOR chip that was tested in our lab. > Datasheet is available at: http://www.issi.com/WW/pdf/25LP-WP080D.pdf > > Testing was done only without the SPI_NOR_{DUAL,QUAD}_READ flags that > were added later, according

Re: [PATCH] perf/x86/intel: Fix minor memleak on Skylake perf initialization

On Wed, 27 Dec 2017, Andi Kleen wrote: > From: Andi Kleen Fixed that yesterday already slightly different.

Re: [RFC] syzbot process

On Thu, Dec 28, 2017 at 1:26 PM, Ozgur wrote: >>> and I think syzbot use to .txt file attached. >>> .txt is not good. >> >> Why are not .txt attachments good? What do you propose to use? > > I think I'm misunderstood that is good to have text output in a file but not >

Re: [PATCH] MAINTAINERS: mark arch/blackfin/ and its gubbins as orphaned

Looping in Arnd as arch maintainer. On Mon, Dec 25, 2017 at 4:38 PM, Adam Borowski wrote: > The blackfin architecture has seen no maintainer action of any kind since > April 2015. No new code, no pull requests, no acks to patches, no response > to mails, nothing. > > The

Re: [PATCH v6 2/8] module: use relative references for __ksymtab entries

On 28 December 2017 at 12:05, Ingo Molnar wrote: > > * Ard Biesheuvel wrote: > >> Annoyingly, we need this because there is a single instance of a >> special section that ends up in the EFI stub code: we build lib/sort.c >> again as a EFI libstub

Re: [PATCH v1] x86/platform/intel-mid: Revert "Make 'bt_sfi_data' const"

* Julia Lawall wrote: > > > [...] There does seem to be a few cases where the field actually does > > > hold an > > > integer. I guess this is not a problem? > > > > Could you point to such an example? > > drivers/thermal/intel_soc_dts_thermal.c:#define

Re: [RFC] syzbot process

28.12.2017, 15:30, "Dmitry Vyukov" : > On Thu, Dec 28, 2017 at 1:26 PM, Ozgur wrote: >   and I think syzbot use to .txt file attached.   .txt is not good. >>> >>>  Why are not .txt attachments good? What do you propose to use? >> >>  I think I'm

[PATCH] module: allow symbol exports to be disabled

To allow existing C code to be incorporated into the decompressor or the UEFI stub, introduce a CPP macro that turns all EXPORT_SYMBOL_xxx declarations into nops, and #define it in places where such exports are undesirable. Note that this gets rid of a rather dodgy redefine of linux/export.h's

Re: BUG: workqueue lockup (2)

On Thu, Dec 21, 2017 at 2:07 PM, Tetsuo Handa wrote: > Dmitry Vyukov wrote: >> On Wed, Dec 20, 2017 at 11:55 AM, Tetsuo Handa >> wrote: >> > Dmitry Vyukov wrote: >> >> On Tue, Dec 19, 2017 at 3:27 PM, Tetsuo Handa >> >>

Re: [PATCH v1] x86/platform/intel-mid: Revert "Make 'bt_sfi_data' const"

On Thu, 28 Dec 2017, Ingo Molnar wrote: > > * Julia Lawall wrote: > > > > > [...] There does seem to be a few cases where the field actually does > > > > hold an > > > > integer. I guess this is not a problem? > > > > > > Could you point to such an example? > > > >

[PATCH v4 04/15] clk: ingenic: Add code to enable/disable PLLs

This commit permits the PLLs to be dynamically enabled and disabled when their children clocks are enabled and disabled. Signed-off-by: Paul Cercueil --- drivers/clk/ingenic/cgu.c | 89 +++ 1 file changed, 74 insertions(+), 15

[PATCH v4 02/15] clk: ingenic: Fix recalc_rate for clocks with fixed divider

Previously, the clocks with a fixed divider would report their rate as being the same as the one of their parent, independently of the divider in use. This commit fixes this behaviour. This went unnoticed as neither the jz4740 nor the jz4780 CGU code have clocks with fixed dividers yet.

Re: [PATCH net-next 1/6] phy: add 2.5G SGMII mode to the phy_mode enum

On 12/28/2017 02:06 AM, Antoine Tenart wrote: > Hi Andrew, > > On Thu, Dec 28, 2017 at 08:20:53AM +0100, Andrew Lunn wrote: >> On Wed, Dec 27, 2017 at 11:14:41PM +0100, Antoine Tenart wrote: >>> This patch adds one more generic PHY mode to the phy_mode enum, to allow >>> configuring generic

[PATCH] pinctrl: tegra: Delete two error messages for a failed memory allocation in tegra_pinctrl_probe()

From: Markus Elfring Date: Thu, 28 Dec 2017 15:15:08 +0100 Omit extra messages for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 19/35] perf annotate: Use perf_env when obtaining the arch name

From: Arnaldo Carvalho de Melo Paving the way to reuse these routines in other areas, like when generating errno tables. Cc: Adrian Hunter Cc: David Ahern Cc: Hendrik Brueckner Cc: Jiri Olsa

[PATCH 28/35] perf test shell: Fix check open filename arg using 'perf trace'

From: Michael Petlan Commit f231af789b11 ("perf test shell: Fix check open filename arg using 'perf trace' on s390x") added an exception for s390x to use openat() instead of open() in the test that intercepts a open syscall to look for the filename argument as obtained by the

[PATCH 26/35] perf probe: Support escaped character in parser

From: Masami Hiramatsu Support the special characters escaped by '\' in parser. This allows user to specify versions directly like below. = # ./perf probe -x /lib64/libc-2.25.so malloc_get_state\\@GLIBC_2.2.5 Added new event: probe_libc:malloc_get_state (on

[PATCH 20/35] perf env: Adopt perf_env__arch() from the annotate code

From: Arnaldo Carvalho de Melo And use it in the libunwind case, with both passing a valid perf_env to extract the arch to be normalized from and passing NULL with the same semantic as in the annotate code: to get it from uname() uts.machine. Now the code to generate per arch

[PATCH 16/35] perf s390: Generate system call table from asm/unistd.h

From: Hendrik Brueckner This should speed up accessing new system calls introduced with the kernel rather than waiting for libaudit updates to include them. Committer testing: $ rm -rf /tmp/build/perf $ mkdir /tmp/build/perf $ make

[PATCH 22/35] perf probe: Cut off the version suffix from event name

From: Masami Hiramatsu Cut off the version suffix (e.g. @GLIBC_2.2.5 etc.) from automatic generated event name. This fixes wildcard event adding like below case; = # perf probe -x /lib64/libc-2.25.so malloc* Internal error: "malloc_get_state@GLIBC_2" is wrong

[PATCH 32/35] perf probe arm64: Fix symbol fixup issues due to ELF type

From: Kim Phillips On an arm64 machine running a CONFIG_RANDOMIZE_BASE=y kernel, perf kernel symbol resolution fails. Debugging saw symsrc_init calling the default elf__needs_adjust_symbols() where checks for an ET_DYN (3) ehdr.e_type failed when they should have

[PATCH 33/35] perf tool: Improve bash command line auto-complete for multiple events with comma

From: Jin Yao perf has perf-completion.sh to define command line auto-completion in bash/zsh. For record/stat -e it works for single events, but isn't working when specifying multiple events with comma. It would be very useful if it could be fixed to make it easier by

[PATCH 35/35] perf tools: Auto-complete for events with ':'

From: Jin Yao It's a follow up patch for a previous patch "perf tool: Return all events as auto-completions after comma". With this patch, auto-completion can work well for events with a ':'. For example: root@skl:/tmp# perf stat -e block:block_

[PATCH 34/35] perf tools: Return all events as auto-completions after comma

From: Jin Yao It's a follow up for one previous patch "perf tool: Improve bash command line auto-complete for multiple events with comma." It fixes an issue that no events are displayed when is directly typed after comma. With this patch, now the result is:

[PATCH 24/35] perf probe: Find versioned symbols from map

From: Masami Hiramatsu Commit d80406453ad4 ("perf symbols: Allow user probes on versioned symbols") allows user to find default versioned symbols (with "@@") in map. However, it did not enable normal versioned symbol (with "@") for perf-probe. E.g. = # ./perf probe

[PATCH 30/35] perf s390: Always build with -fPIC

From: Hendrik Brueckner On s390, object files must be compiled with position-indepedent code in order to be incrementally linked or linked to shared libraries. Therefore, add -fPIC to the CFLAGS for s390 to ensure each object file is built properly. Reported-by:

[PATCH 17/35] perf trace: Use generated syscall table on s390 too

From: Hendrik Brueckner This should speed up accessing new system calls introduced with the kernel rather than waiting for libaudit updates to include them. It also enables users to specify wildcards, for example, perf trace -e 'open*', just like was already

Re: [PATCH v5 5/5] iommu/vt-d: Add debugfs support for Interrupt remapping

On Thu, 2017-12-21 at 16:32 -0800, Sohil Mehta wrote: > + seq_puts(m, "\n"); seq_putc() > + seq_puts(m, "\n"); Ditto. -- Andy Shevchenko Intel Finland Oy

Re: [PATCH v5 2/5] iommu/vt-d: Add debugfs support to show context internals

On Thu, 2017-12-21 at 16:32 -0800, Sohil Mehta wrote: > From: Gayatri Kammela > > IOMMU internals states such as root and context can be exported to the > userspace. > > Example of such dump in Kabylake: > v5: Change to a SPDX license tag > Fix seq_printf

Re: [PATCH] platform/x86: silead_dmi: Add entry for the Trekstor Primebook C13

On Mon, Dec 25, 2017 at 2:45 PM, Hans de Goede wrote: > Add touchscreen platform data for the Trekstor Primebook C13 laptop. > Pushed to my review and testing queue, thanks! Note, the rest now on it's way to for-next (via testing) > Signed-off-by: Hans de Goede

[PATCH 2/3] mmc: sdhci: Add support for o2 eMMC HS200 mode and hardware tuning

Add register definition for eMMC HS200 mode. Add bitmask definition for hardware tuning function. Signed-off-by: ernest.zhang --- drivers/mmc/host/sdhci-pci-o2micro.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/mmc/host/sdhci-pci-o2micro.h

[PATCH 3/3] mmc: sdhci: fix o2 eMMC init bug and add support for hardware tuning

In some case of eMMC used as boot device, the eMMC signaling voltage is fixed to 1.8v, bios can set o2 sd host controller register 0x308 bit4 to let host controller skip try 3.3.v signaling voltage in eMMC initialize process. O2 sd host controller has a function named hardware tuning. In software

Re: [RFC] syzbot process

On Thu, Dec 21, 2017 at 6:05 PM, Greg Kroah-Hartman wrote: > On Thu, Dec 21, 2017 at 01:52:40PM +0100, Dmitry Vyukov wrote: >> Hello, >> >> You might have seen bug reports coming from syzbot on LKML recently. >> syzbot is an automated system that continuously fuzzes

[PATCH] staging: ccree: ssi_hash: remove unnecessary parentheses

Fixed a coding style issue Signed-off-by: Elad Wexler --- drivers/staging/ccree/ssi_hash.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/ccree/ssi_hash.c b/drivers/staging/ccree/ssi_hash.c index 2035835..8d56fa7 100644 ---

Re: PROBLEM: 4.15.0-rc3 APIC causes lockups on Core 2 Duo laptop

Hi Alexandru, At 12/28/2017 10:51 AM, Alexandru Chirvasitu wrote: Ah, of course. Attached is the output of `journalctl --boot=-1` after booting, getting locked up, and then rebooting a good kernel. For the Hard lockups on both CPUs after login: Please try the patch in the attachment by git

Re: [PATCH v1] x86/platform/intel-mid: Revert "Make 'bt_sfi_data' const"

On Thu, 28 Dec 2017, Ingo Molnar wrote: > > * Andy Shevchenko wrote: > > > The annoying static analyzer follow up patches make a pain rather then > > fixing issues. > > > > The one done by commit 276c87054751 > > > > ("x86/platform/intel-mid: Make

[PATCH v4 3/4] dt-bindings: at24: extend the list of supported chips

Add other variants of at24 EEPROMs we support in the driver to the list of allowed compatible fallbacks. Signed-off-by: Bartosz Golaszewski Reviewed-by: Javier Martinez Canillas --- Documentation/devicetree/bindings/eeprom/at24.txt | 9 + 1 file

[PATCH v4 4/4] eeprom: at24: extend the list of chips supported in DT

Add all supported at24 variants to the of_match table. Signed-off-by: Bartosz Golaszewski Reviewed-by: Javier Martinez Canillas --- drivers/misc/eeprom/at24.c | 9 + 1 file changed, 9 insertions(+) diff --git a/drivers/misc/eeprom/at24.c

[PATCH v4 0/4] eeprom: at24: device tree support fixes

The first three patches fix certain issues with the DT binding document. The last two extend the device tree support in the driver with more at24 EEPROM variants. v1 -> v2: - remove any implementation details from patch 1/5 v2 -> v3: - reword patch 1/5: allow any "," pair as long as a

[PATCH v4 2/4] dt-bindings: at24: fix formatting and style

Make formatting and style consistent for the entire document. This patch doesn't change the content of the binding. Signed-off-by: Bartosz Golaszewski Reviewed-by: Javier Martinez Canillas --- Documentation/devicetree/bindings/eeprom/at24.txt | 22

[PATCH IMPROVEMENT] block, bfq: limit sectors served with interactive weight raising

To maximise responsiveness, BFQ raises the weight, and performs device idling, for bfq_queues associated with processes deemed as interactive. In particular, weight raising has a maximum duration, equal to the time needed to start a large application. If a weight-raised process goes on doing I/O

[RFC patch] ioremap: don't set up huge I/O mappings when p4d/pud/pmd is zero

From: Hanjun Guo When we using iounmap() to free the 4K mapping, it just clear the PTEs but leave P4D/PUD/PMD unchanged, also will not free the memory of page tables. This will cause issues on ARM64 platform (not sure if other archs have the same issue) for this case: 1.

[tip:irq/urgent] genirq: Guard handle_bad_irq log messages

Commit-ID: 11bca0a83f83f6093d816295668e74ef24595944 Gitweb: https://git.kernel.org/tip/11bca0a83f83f6093d816295668e74ef24595944 Author: Guenter Roeck AuthorDate: Sat, 2 Dec 2017 09:13:04 -0800 Committer: Thomas Gleixner CommitDate: Thu, 28 Dec

Re: [PATCH 1/4] ASoC: mediatek: fix error handling in mt2701_afe_pcm_dev_probe()

Sorry, please ignore this series. I will send new ones later. On Mon, 2017-12-25 at 16:28 +0800, Ryder Lee wrote: > Fix unbalanced error handling path which will get incorrect counts > if probe failed. The .remove() should be adjusted accordingly. > > Signed-off-by: Ryder Lee

Re: [RFC] syzbot process

28.12.2017, 14:45, "Dmitry Vyukov" : > On Thu, Dec 28, 2017 at 11:51 AM, Ozgur wrote: >>  28.12.2017, 13:41, "Dmitry Vyukov" : >>>  On Fri, Dec 22, 2017 at 4:32 AM, Eric Biggers wrote:   On Thu, Dec 21, 2017 at

[PATCH 1/3] serial: core: Make uart_parse_options take const char* argument

The pointed string is never modified from within uart_parse_options, so it should be marked as const in the function prototype. Signed-off-by: Paul Cercueil --- drivers/tty/serial/serial_core.c | 5 +++-- include/linux/serial_core.h | 2 +- 2 files changed, 4

[PATCH] pinctrl: sunxi: fix a typo when merging A20 support to A10 driver

When merging A20 pinctrl support to A10 pinctrl driver, the I2C function of PI3 is wrongly written as "i2c3" (it should be "i2c4"). Fix this typo. Fixes: cad4e209c102 ("pinctrl: sunxi: add support of R40 to A10 pinctrl driver") Reported-by: Mark Kettenis Signed-off-by:

[PATCH v2 3/9] v4l: platform: Add Renesas CEU driver

Add driver for Renesas Capture Engine Unit (CEU). The CEU interface supports capturing 'data' (YUV422) and 'images' (NV[12|21|16|61]). This driver aims to replace the soc_camera-based sh_mobile_ceu one. Tested with ov7670 camera sensor, providing YUYV_2X8 data on Renesas RZ platform GR-Peach.

[PATCH v2 2/9] include: media: Add Renesas CEU driver interface

Add renesas-ceu header file. Do not remove the existing sh_mobile_ceu.h one as long as the original driver does not go away. Signed-off-by: Jacopo Mondi --- include/media/drv-intf/renesas-ceu.h | 20 1 file changed, 20 insertions(+) create mode

[GIT PULL 00/35] perf/core improvements and fixes

Hi Ingo, Please consider pulling, - Arnaldo Test results at the end of this message, as usual. The following changes since commit faaf95677f33dac910b6cbe917cabea43c8c1616: Merge branch 'perf/urgent' into perf/core, to pick up fixes (2017-12-18 18:13:00 +0100) are available in the

[PATCH 01/35] perf stat: Define a structure for per-thread shadow stats

From: Jin Yao Perf has a set of static variables to record the runtime shadow metrics stats. While if we want to record the runtime shadow stats for per-thread, it will be the limitation. This patch creates a structure and the next patches will use this structure to

Re: [PATCH bpf-next v3 1/3] libbpf: add function to setup XDP

On 2017/12/28 17:04, Eric Leblond wrote: > Most of the code is taken from set_link_xdp_fd() in bpf_load.c and > slightly modified to be library compliant. > > Signed-off-by: Eric Leblond > Acked-by: Alexei Starovoitov > --- ... > +int bpf_set_link_xdp_fd(int

Re: [Ocfs2-devel] [PATCH v2] ocfs2: try a blocking lock before return AOP_TRUNCATED_PAGE

Hi Gang, It looks good to me. Thanks, Changwei On 2017/12/28 15:49, Gang He wrote: > If we can't get inode lock immediately in the function > ocfs2_inode_lock_with_page() when reading a page, we should not > return directly here, since this will lead to a softlockup problem > when the kernel is

Re: [PATCH] objtool: Fix clang enum conversion warning

On Wed, 27 Dec 2017, Josh Poimboeuf wrote: The patch from Lukas was the first one I received, so that's the one I used. I rewrote the commit msg for clarity and added my SOB and sent it to Ingo for merging. Josh, Ingo, the first patch I sent to Josh must have been a v0, which I probably

[PATCH] Input: misc: Kconfig: fixed a spelling mistake

fixed a spelling mistake: buttong -> button Signed-off-by: Zhuohua Li --- drivers/input/misc/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/input/misc/Kconfig b/drivers/input/misc/Kconfig index 9f082a388388..509ba8ef1464 100644 ---

Re: [PATCH net-next 5/6] arm64: dts: marvell: mcbin: enable the fourth network interface

Hi Russell, On Wed, Dec 27, 2017 at 11:20:00PM +, Russell King - ARM Linux wrote: > On Wed, Dec 27, 2017 at 11:42:52PM +0100, Antoine Tenart wrote: > > > > What do you suggest to describe this in the dt, to enable a port using > > the current PPv2 driver? > > I don't - I'm merely pointing

[PATCH v3] mtd: spi-nor: Add ISSI is25lp080d support

Add support for a new ISSI 1MB SPI NOR chip that was tested in our lab. Datasheet is available at: http://www.issi.com/WW/pdf/25LP-WP080D.pdf Testing was done only without the SPI_NOR_{DUAL,QUAD}_READ flags that were added later, according to the datasheet. Tested-by: Pascal Fabreges

Re: [PATCH net-next 5/6] arm64: dts: marvell: mcbin: enable the fourth network interface

Hi Andrew, On Thu, Dec 28, 2017 at 08:46:23AM +0100, Andrew Lunn wrote: > On Wed, Dec 27, 2017 at 10:24:01PM +, Russell King - ARM Linux wrote: > > On Wed, Dec 27, 2017 at 11:14:45PM +0100, Antoine Tenart wrote: > > > > > > +_eth2 { > > > + /* CPS Lane 5 */ > > > + status = "okay"; > > > +

Re: [RFC] syzbot process

On Thu, Dec 21, 2017 at 2:36 PM, Stephan Mueller wrote: > Am Donnerstag, 21. Dezember 2017, 14:22:40 CET schrieb Andrey Ryabinin: > > Hi Andrey, > >> 2017-12-21 15:52 GMT+03:00 Dmitry Vyukov : >> > Any other proposals, thoughts, ideas? >> >> a) Assume that

[PATCH v4 1/4] dt-bindings: at24: consistently document the compatible property

Current description of the compatible property for at24 is quite vague. State explicitly that any "," pair is accepted as long as a correct fallback is used for non-atmel chips. Signed-off-by: Bartosz Golaszewski --- Documentation/devicetree/bindings/eeprom/at24.txt | 58

Re: [RFC] syzbot process

28.12.2017, 13:41, "Dmitry Vyukov" : > On Fri, Dec 22, 2017 at 4:32 AM, Eric Biggers wrote: >>  On Thu, Dec 21, 2017 at 01:52:40PM +0100, Dmitry Vyukov wrote: >>>  However, the cost is that it needs to understand statuses of bugs: >>>  most importantly,

Re: [PATCH v3 14/16] phy: Add notify_speed callback

Hi, On Wednesday 20 December 2017 02:11 PM, Manu Gautam wrote: > Hi > > > On 12/20/2017 12:47 PM, Kishon Vijay Abraham I wrote: >> Hi, >> > [snip] Why not use a notification mechanism instead of adding new APIs in phy-core. This will only bloat phy-core with APIs for a

Re: [PATCH 1/3] phy: phy-mtk-tphy: use auto instead of force to bypass utmi signals

On Thursday 07 December 2017 05:23 PM, Chunfeng Yun wrote: > When system is running, if usb2 phy is forced to bypass utmi signals, > all PLL will be turned off, and it can't detect device connection > anymore, so replace force mode with auto mode which can bypass utmi > signals automatically if

Re: [PATCH 0/4] Bug fixes for the Broadcom STB USB phy driver

On Thursday 28 December 2017 12:58 AM, Al Cooper wrote: > This patchset contains a series of bug fixes for the Broadcom > STB USB phy driver. removed usb from subject and merged to phy -next. Thanks Kishon > > Al Cooper (4): > phy: usb: phy-brcm-usb: Fix two DT properties to match bindings

Re: v4.15: camera problems on n900

On Wed 2017-12-27 23:17:19, Sakari Ailus wrote: > On Wed, Dec 27, 2017 at 10:05:43PM +0100, Pavel Machek wrote: > > Hi! > > > > In v4.14, back camera on N900 works. On v4.15-rc1.. it works for few > > seconds, but then I get repeated oopses. > > > > On v4.15-rc0.5 (commit

[tip:x86/urgent] x86/apic: Avoid wrong warning when parsing 'apic=' in X86-32 case

Commit-ID: 4fcab6693445cfb84f2b65868c58043535090e52 Gitweb: https://git.kernel.org/tip/4fcab6693445cfb84f2b65868c58043535090e52 Author: Dou Liyang AuthorDate: Mon, 4 Dec 2017 12:03:12 +0800 Committer: Thomas Gleixner CommitDate: Thu, 28

Re: [PATCH v1] x86/platform/intel-mid: Revert "Make 'bt_sfi_data' const"

On Thu, 28 Dec 2017, Ingo Molnar wrote: > > * Julia Lawall wrote: > > > > > > > On Thu, 28 Dec 2017, Ingo Molnar wrote: > > > > > > > > * Andy Shevchenko wrote: > > > > > > > On Thu, 2017-12-28 at 11:28 +0100, Ingo Molnar wrote: > > > >

Re: [PATCH v2 0/9] PCI: Add support to the Cadence PCIe controller

Hi Cyrille, On Monday 18 December 2017 11:46 PM, Cyrille Pitchen wrote: > Hi all, > > this series of patches adds support to the Cadence PCIe controller. > It was tested on a ARM64 platform emulated by a Palladium running the > pci-next kernel. > > The host mode was tested with some PCIe

Re: niced tasks on SMT system

On Thu, 2017-12-28 at 13:10 +0100, Pavel Machek wrote: > Hi! > > Ok, so I'm compiling, and I'd like to run a flight simulator. > > Flightgear normally does 20fps on my system... kinda low but playable. > > I have reniced make -j 5 fo kernel running. Scheduler gives 100% of > one of CPUs to

[PATCH] cifs: add .splice_write

add splice_write support in cifs vfs using iter_file_splice_write Signed-off-by: Andrés Souto --- fs/cifs/cifsfs.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/fs/cifs/cifsfs.c b/fs/cifs/cifsfs.c index 8c8b75d3..ba2986bd 100644 --- a/fs/cifs/cifsfs.c +++

[PATCH v4 13/15] MIPS: JZ4770: Workaround for corrupted DMA transfers

From: Maarten ter Huurne We have seen MMC DMA transfers read corrupted data from SDRAM when a burst interval ends at physical address 0x1000. To avoid this problem, we remove the final page of low memory from the memory map. Signed-off-by: Maarten ter Huurne

[PATCH v4 07/15] MIPS: Setup boot_command_line before plat_mem_setup

From: Paul Burton Platforms using DT will typically call __dt_setup_arch from plat_mem_setup. This in turn calls early_init_dt_scan. When CONFIG_CMDLINE is set, this leads to its value being copied into boot_command_line by early_init_dt_scan_chosen. If this happens

[PATCH v4 12/15] MIPS: JZ4770: Work around config2 misreporting associativity

From: Maarten ter Huurne According to config2, the associativity would be 5-ways, but the documentation states 4-ways, which also matches the documented L2 cache size of 256 kB. Signed-off-by: Maarten ter Huurne --- arch/mips/mm/sc-mips.c | 9

[PATCH v4 10/15] MIPS: ingenic: Add machine info for supported boards

This makes sure that 'mips_machtype' will be initialized to the SoC version used on the board. Signed-off-by: Paul Cercueil --- arch/mips/Kconfig | 1 + arch/mips/jz4740/Makefile | 2 +- arch/mips/jz4740/boards.c | 16 arch/mips/jz4740/setup.c |

[PATCH v4 11/15] MIPS: ingenic: Initial JZ4770 support

Provide just enough bits (clocks, clocksource, uart) to allow a kernel to boot on the JZ4770 SoC to a initramfs userspace. Signed-off-by: Paul Cercueil --- arch/mips/boot/dts/ingenic/jz4770.dtsi | 210 + arch/mips/jz4740/Kconfig

[PATCH v4 08/15] MIPS: ingenic: Use common cmdline handling code

From: Paul Burton jz4740_init_cmdline appends all arguments from argv (in fw_arg1) to arcs_cmdline, up to argc (in fw_arg0). The common code in fw_init_cmdline will do the exact same thing when run on a system where fw_arg0 isn't a pointer to kseg0 (it'll also set

[PATCH v4 09/15] MIPS: platform: add machtype IDs for more Ingenic SoCs

Add a machtype ID for the JZ4780 SoC, which was missing, and one for the newly supported JZ4770 SoC. Signed-off-by: Paul Cercueil --- arch/mips/include/asm/bootinfo.h | 2 ++ 1 file changed, 2 insertions(+) v2: No change v3: No change v4: No change diff --git

[PATCH v4 15/15] MIPS: ingenic: Initial GCW Zero support

The GCW Zero (http://www.gcw-zero.com) is a retro-gaming focused handheld game console, successfully kickstarted in ~2012, running Linux. Signed-off-by: Paul Cercueil --- arch/mips/boot/dts/ingenic/Makefile | 1 + arch/mips/boot/dts/ingenic/gcw0.dts | 60

[PATCH v4 03/15] clk: ingenic: support PLLs with no bypass bit

The second PLL of the JZ4770 does not have a bypass bit. This commit makes it possible to support it with the current common CGU code. Signed-off-by: Paul Cercueil --- drivers/clk/ingenic/cgu.c | 3 ++- drivers/clk/ingenic/cgu.h | 2 ++ 2 files changed, 4 insertions(+), 1

[PATCH v4 06/15] clk: Add Ingenic jz4770 CGU driver

Add support for the clocks provided by the CGU in the Ingenic JZ4770 SoC. Signed-off-by: Paul Cercueil Signed-off-by: Maarten ter Huurne --- drivers/clk/ingenic/Makefile | 1 + drivers/clk/ingenic/jz4770-cgu.c | 487

Re: WARNING in __wake_up_common

On Thu, Dec 28, 2017 at 10:30:46AM +0100, Dmitry Vyukov wrote: > On Thu, Dec 28, 2017 at 10:20 AM, syzbot > wrote: > > Hello, > > > > syzkaller hit the following crash on > > 82bcf1def3b5f1251177ad47c44f7e17af039b4b > >

[PATCH 09/35] perf thread_map: Enumerate all threads from /proc

From: Jin Yao This patch calls thread_map__new_all_cpus() to enumerate all threads from /proc if per-thread flag is enabled. Signed-off-by: Jin Yao Acked-by: Jiri Olsa Cc: Alexander Shishkin

[PATCH 11/35] perf stat: Resort '--per-thread' result

From: Jin Yao There are many threads reported if we enable '--per-thread' globally. 1. Most of the threads are not counted or counting value 0. This patch removes these threads. 2. We also resort the threads in display according to the counting value. It's useful for

[PATCH 12/35] perf utils: Move is_directory() to path.h

From: Jiri Olsa So that it can be used more widely, like in the next patch, when it will be used to fix a bug in 'perf test' handling of dirent.d_type == DT_UNKNOWN. Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Michael Petlan

[PATCH 05/35] perf stat: Print per-thread shadow stats

From: Jin Yao The function perf_stat__print_shadow_stats() is called to print the shadow stats on a set of static variables. But the static variables are the limitations to support per-thread shadow stats. This patch lets the perf_stat__print_shadow_stats() support to

[PATCH 06/35] perf stat: Remove a set of shadow stats static variables

From: Jin Yao In previous patches, we have reconstructed the code and let it not access the static variables directly. This patch removes these static variables. Signed-off-by: Jin Yao Acked-by: Jiri Olsa Cc: Alexander

[PATCH 03/35] perf stat: Create the runtime_stat init/exit function

From: Jin Yao It mainly initializes and releases the rblist which is defined in struct runtime_stat. For the original rblist 'runtime_saved_values', it's still kept there for keeping the patch bisectable. The rblist 'runtime_saved_values' will be removed in later patch

[PATCH 04/35] perf stat: Update per-thread shadow stats

From: Jin Yao The functions perf_stat__update_shadow_stats() is called to update the shadow stats on a set of static variables. But the static variables are the limitations to be extended to support per-thread shadow stats. This patch lets the

[PATCH 10/35] perf stat: Remove --per-thread pid/tid limitation

From: Jin Yao Currently, if we execute 'perf stat --per-thread' without specifying pid/tid, perf will return error. root@skl:/tmp# perf stat --per-thread The --per-thread option is only available when monitoring via -p -t options. -p, --pidstat events on

  1   2   3   4   5   6   7   8   9   10   >