Re: [PATCH v3] PCI / PM: Always check PME wakeup capability for runtime wakeup support

On Thursday, April 26, 2018 8:54:14 AM CEST Kai Heng Feng wrote: > > > On Apr 13, 2018, at 3:29 PM, Rafael J. Wysocki wrote: > > > > On Friday, April 13, 2018 8:58:11 AM CEST Kai Heng Feng wrote: > >> Hi Bjorn and Rafael, > >> > >>> On Apr 1, 2018, at 12:40 AM, Kai-Heng Feng > >>> wrote: > >>> >

RE: [PATCH 4/5] ARM: dts: imx6sx-sabreauto: add fec support

Hi, Fabio Anson Huang Best Regards! > -Original Message- > From: Fabio Estevam [mailto:feste...@gmail.com] > Sent: Wednesday, April 25, 2018 9:47 PM > To: Anson Huang > Cc: Shawn Guo ; Sascha Hauer > ; Fabio Estevam ; Rob > Herring ; Mark Rutland ; > dl-linux-imx ; moderated list:ARM/FR

Re: [PATCH v3] PCI / PM: Always check PME wakeup capability for runtime wakeup support

On Apr 13, 2018, at 3:29 PM, Rafael J. Wysocki wrote: On Friday, April 13, 2018 8:58:11 AM CEST Kai Heng Feng wrote: Hi Bjorn and Rafael, On Apr 1, 2018, at 12:40 AM, Kai-Heng Feng wrote: USB controller ASM1042 stops working after commit de3ef1eb1cd0 ("PM / core: Drop run_wake flag from s

Re: [PATCH 4.9 75/95] random: set up the NUMA crng instances after the CRNG is fully initialized

Oh, pull request was already sent. Should be merged shortly. https://marc.info/?l=linux-kernel&m=152472466201090&w=2

Re: [GIT PULL] Immutable branch between MFD, Input and RTC due for the v4.18 merge window

On Mon, 2018-04-16 at 15:18 +0100, Lee Jones wrote: > Enjoy! > > The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338: > > Linux 4.17-rc1 (2018-04-15 18:24:20 -0700) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.

Re: [tip:timers/urgent] Revert: Unify CLOCK_MONOTONIC and CLOCK_BOOTTIME

On Wednesday, April 25, 2018 10:19:08 PM CEST Pavel Machek wrote: > > --J2SCkAp4GZ/dPZZf > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Wed 2018-04-25 12:41:23, Linus Torvalds wrote: > > On Wed, Apr 25, 2018 at 12:09

Re: [PATCH v4 2/2] media: Add a driver for the ov7251 camera sensor

Hi Todor, On Wed, Apr 25, 2018 at 07:20:46PM +0300, Todor Tomov wrote: ... > +static int ov7251_write_reg(struct ov7251 *ov7251, u16 reg, u8 val) > +{ > + u8 regbuf[3]; > + int ret; > + > + regbuf[0] = reg >> 8; > + regbuf[1] = reg & 0xff; > + regbuf[2] = val; > + > + ret =

Re: [RFC PATCH RESEND 3/3] pinctrl: upboard: Add UP2 pinctrl and gpio driver

On Sat, 21 Apr 2018, Javier Arteaga wrote: > The UP2 board features a Raspberry Pi compatible pin header (HAT) and a > board-specific expansion connector (EXHAT). Both expose assorted > functions from either the SoC (such as GPIO, I2C, SPI, UART...) or other > on-board devices (ADC, FPGA IP blocks

Re: [tip:timers/urgent] Revert: Unify CLOCK_MONOTONIC and CLOCK_BOOTTIME

On Thursday, April 26, 2018 12:41:40 AM CEST Steven Rostedt wrote: > On Wed, 25 Apr 2018 22:57:12 +0200 > "Rafael J. Wysocki" wrote: > > > FWIW, I run (64-bit) OpenSUSE 42.3 on the failing machine (Acer Aspire S5) > > with > > my own kernel (custom config based on the distro one). > > > > The p

Re: [PATCH 4.9 75/95] random: set up the NUMA crng instances after the CRNG is fully initialized

Ingo Molnar wrote: > What\'s the resolution here? It\'s still triggering upstream as well, as of > 69bfd470f462: > > [8.881634] dracut: Switching root > > [8.994899] > [8.999338] WARNING: inconsistent lock state > [9.003760] 4.17.0-rc2-00151-g43ae

Re: [PATCH 06/22] arc: use generic dma_noncoherent_ops

On Wed, Apr 25, 2018 at 11:17:01AM +, Alexey Brodkin wrote: > Which is actually strange as I would expect ARC code to be built by bots. I don't think I got any notification. Thank for the fixes! I think I found the bug, based on the fact that so far all tests for architectures that also need

Re: [PATCH 13/22] nds32: use generic dma_noncoherent_ops

Can you try this patch ontop of either the new or original one? --- diff --git a/lib/dma-noncoherent.c b/lib/dma-noncoherent.c index f4b8532c20ac..a2c192b3508d 100644 --- a/lib/dma-noncoherent.c +++ b/lib/dma-noncoherent.c @@ -48,7 +48,7 @@ static int dma_noncoherent_map_sg(struct device *dev, str

AW: [PATCH v2] Input: add bu21029 touch driver

Hello, > Betreff: [PATCH v2] Input: add bu21029 touch driver > > From: Zhu Yi > > Add Rohm BU21029 resistive touch panel controller support with I2C > interface. > > Signed-off-by: Zhu Yi > Signed-off-by: Mark Jonas > Reviewed-by: Heiko Schocher > --- > Changes in v2: > - make ABS_PRESSURE

[PATCH 3/3] [media] cxd2880: Changed version information

From: Yasunari Takiguchi This is the version update for this cxd2880 driver changing. Signed-off-by: Yasunari Takiguchi Signed-off-by: Masayuki Yamamoto Signed-off-by: Hideki Nozawa Signed-off-by: Kota Yonezawa Signed-off-by: Toshihiko Matsumoto Signed-off-by: Satoshi Watanabe --- [Chang

[GIT PULL] /dev/random fixes for 4.17-rc3

The following changes since commit d848e5f8e1ebdb227d045db55fe4f825e82965fa: random: add new ioctl RNDRESEEDCRNG (2018-04-14 11:59:31 -0400) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random.git tags/random_for_linus_stable for you to fetch

[PATCH 2/3] [media] cxd2880:Optimized spi drive current and BER/PER set/get condition

From: Yasunari Takiguchi This is the optimization for SPI drive current and signal lock condition check part for BER/PER measure to ensure BER/PER are stable Signed-off-by: Yasunari Takiguchi Signed-off-by: Masayuki Yamamoto Signed-off-by: Hideki Nozawa Signed-off-by: Kota Yonezawa Signed-o

[PATCH 1/3] [media] cxd2880-spi: Modified how to declare structure

From: Yasunari Takiguchi This is the modification of structure declaration for spi_transfer. Signed-off-by: Yasunari Takiguchi Signed-off-by: Masayuki Yamamoto Signed-off-by: Hideki Nozawa Signed-off-by: Kota Yonezawa Signed-off-by: Toshihiko Matsumoto Signed-off-by: Satoshi Watanabe ---

Re: [PATCH] drm/bridge/synopsys: dsi: use adjusted_mode in mode_set

On 25.01.2018 16:55, Philippe Cornu wrote: > The "adjusted_mode" clock value (ie the real pixel clock) is more > accurate than "mode" clock value (ie the panel/bridge requested > clock value). It offers a better preciseness for timing > computations and allows to reduce the extra dsi bandwidth in >

[PATCH 0/3] [media] cxd2880: modified structure declaration and optimized the driver

From: Yasunari Takiguchi Hi, This is the update patch for patch Sony CXD2880 DVB-T2/T tuner + demodulator driver. We modified how to declare structure and optimized spi drive current and signal lock condition check part for BER/PER measure to ensure BER/PER are stable. The change history of

RE: [PATCH V4 3/6] ARM: dts: imx6sx-sabreauto: add IO expander max7310 support

Anson Huang Best Regards! > -Original Message- > From: Fabio Estevam [mailto:feste...@gmail.com] > Sent: Thursday, April 26, 2018 2:21 PM > To: Anson Huang > Cc: Shawn Guo ; Sascha Hauer > ; Fabio Estevam ; Rob > Herring ; Mark Rutland ; > Russell King - ARM Linux ; dl-linux-imx > ; mo

Re: [PATCH] PM / Sleep: only update last time for active wakeup sources

On Thu, Apr 26, 2018 at 1:40 AM, Doug Berger wrote: > When wakelock support was added, the wakeup_source_add() function > was updated to set the last_time value of the wakeup source. This > has the unintended side effect of producing confusing output from > pm_print_active_wakeup_sources() when a

[PATCH] NET: usb: qmi_wwan: add support for ublox R410M PID 0x90b2

This patch adds support for PID 0x90b2 of ublox R410M. qmicli -d /dev/cdc-wdm0 --dms-get-manufacturer [/dev/cdc-wdm0] Device manufacturer retrieved: Manufacturer: 'u-blox' qmicli -d /dev/cdc-wdm0 --dms-get-model [/dev/cdc-wdm0] Device model retrieved: Model: 'SARA-R410M-02B' Sign

[PATCH] USB: serial: option: adding support for ublox R410M

This patch adds support for ublox R410M PID 0x90b2 USB modem to option driver, this module supports LTE Cat M1 / NB1. Interface layout: 0: QCDM/DIAG 1: ADB 2: AT 3: RMNET Signed-off-by: SZ Lin (林上智) Cc: stable --- Please refer to following lsusb output: Bus 001 Device 003: ID 05c6:90b2 Qualco

Re: [RFC 0/2] dw_mmc: add multislot support

[...] > A bit remark for better understanding: > > All card settings change are serialized too. These settings are applied > after slot switch before execution of new request for this slot. > > So situations like calling any host_0 ops while another host (host_1) is > active > are handled by curr

Re: [PATCH v8 09/13] [media] vb2: add in-fence support to QBUF

On 04/25/2018 10:11 PM, Ezequiel Garcia wrote: > On 14 March 2018 at 12:55, Hans Verkuil wrote: >> On 03/09/2018 09:49 AM, Gustavo Padovan wrote: >>> From: Gustavo Padovan >>> >>> Receive in-fence from userspace and add support for waiting on them >>> before queueing the buffer to the driver. Buf

Kconfig:12: can't open file "arch/tile/Kconfig"

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 69bfd470f4623d2d57ad62cb33791cded0c662f4 commit: bb9d812643d8a121df7d614a2b9c60193a92deb0 arch: remove tile port date: 6 weeks ago config: tile-allmodconfig compiler: tilegx-linux-gcc (GCC) 7.2.0 reproduce:

Re: [PATCH] net: phy: marvell: clear wol event before setting it

Hi, On 4/26/2018 11:45 AM, Jisheng Zhang wrote: Hi, On Thu, 26 Apr 2018 11:10:21 +0530 Bhadram Varka wrote: Hi, On 4/19/2018 5:48 PM, Andrew Lunn wrote: On Thu, Apr 19, 2018 at 04:02:32PM +0800, Jisheng Zhang wrote: From: Jingju Hou If WOL event happened once, the LED[2] interrupt pin wil

Re: [PATCH 8/8] ALSA: add new 32-bit layout for snd_pcm_mmap_status/control

Hi Arnd, I love your patch! Perhaps something to improve: [auto build test WARNING on v4.17-rc2] [cannot apply to sound/for-next asoc/for-next arm-soc/for-next next-20180424] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://gith

[GIT PULL] s390 patches for 4.17-rc3

Hi Linus, please pull from the 'for-linus' branch of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus to receive the following updates: A couple of bug fixes: * Correct some CPU-MF counter names for z13 and z14 * Correct locking in the vfio-ccw fsm_io_helper

Re: [PATCH V4 3/6] ARM: dts: imx6sx-sabreauto: add IO expander max7310 support

On Thu, Apr 26, 2018 at 12:06 AM, Anson Huang wrote: > MAX7310 pins are for PCIe, CAN, MLB. GPS etc., these modules are NOT enabled > yet, so > I can NOT test it, I think we should add MAX7310 users when these modules are > enabled, > ethernet PHY is NOT controlled by it. You said previously t

Re: [PATCH 8/8] ALSA: add new 32-bit layout for snd_pcm_mmap_status/control

Hi Arnd, I love your patch! Yet something to improve: [auto build test ERROR on v4.17-rc2] [cannot apply to sound/for-next asoc/for-next arm-soc/for-next next-20180424] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

Re: [PATCH] net: phy: marvell: clear wol event before setting it

Hi, On Thu, 26 Apr 2018 11:10:21 +0530 Bhadram Varka wrote: > Hi, > > On 4/19/2018 5:48 PM, Andrew Lunn wrote: > > On Thu, Apr 19, 2018 at 04:02:32PM +0800, Jisheng Zhang wrote: > >> From: Jingju Hou > >> > >> If WOL event happened once, the LED[2] interrupt pin will not be > >> cleared unles

Re: WARNING: kobject bug in br_add_if

On Wed, Apr 11, 2018 at 05:18:23PM +0200, Dmitry Vyukov wrote: > On Wed, Apr 11, 2018 at 5:15 PM, syzbot > wrote: > > Hello, > > > > syzbot hit the following crash on upstream commit > > 10b84daddbec72c6b440216a69de9a9605127f7a (Sat Mar 31 17:59:00 2018 +) > > Merge branch 'perf-urgent-for-lin

Re: [PATCH 2/2] ARM: dts: r8a7740: Enable CEU0

Thanks Jacopo, I'm very pleased to see this series. On Wed, Apr 25, 2018 at 01:15:20PM +0200, Jacopo Mondi wrote: > Enable CEU0 peripheral for Renesas R-Mobile A1 R8A7740. Given 'status = "disabled"' below I think you are describing but not enabling CEU0. Also in the subject. Should we also des

Re: Moving unmaintained filesystems to staging

On Wed 2018-04-25 08:46:02, Matthew Wilcox wrote: > Recently ncpfs got moved to staging. Also recently, we had some fuzzer > developers report bugs in hfs, which they deem a security hole because > Ubuntu attempts to automount an inserted USB device as hfs. We promise "no-regressions" for code in

[PATCH] x86/vector: Remove the unused macro FPU_IRQ

The macro FPU_IRQ has never been used since v3.10, So remove it. Signed-off-by: Dou Liyang --- arch/x86/include/asm/irq_vectors.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/x86/include/asm/irq_vectors.h b/arch/x86/include/asm/irq_vectors.h index 57003074bd7a..548d90bbf919 100644

Re: [PATCH 4.9 75/95] random: set up the NUMA crng instances after the CRNG is fully initialized

* Theodore Y. Ts'o wrote: > On Mon, Apr 23, 2018 at 07:21:10PM +0900, Tetsuo Handa wrote: > > Greg Kroah-Hartman wrote: > > > > I think this can be fixed by backporting commit 4a072c71f49b > > > > "random: silence compiler warnings and fix race" but I'm not sure > > > > whether that depends on o

Re: [PATCH 4.16 00/26] 4.16.5-stable review

On Wed, Apr 25, 2018 at 12:36:05PM -0600, Shuah Khan wrote: > On 04/25/2018 04:33 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.16.5 release. > > There are 26 patches in this series, all will be posted as a response > > to this one. If anyone has any issu

[tip:perf/urgent] perf stat: Fix duplicate PMU name for interval print

Commit-ID: 80ee8c588afde077cb0439e15129579a267916c4 Gitweb: https://git.kernel.org/tip/80ee8c588afde077cb0439e15129579a267916c4 Author: Kan Liang AuthorDate: Tue, 24 Apr 2018 11:20:14 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 24 Apr 2018 16:12:00 -0300 perf stat: Fix d

Re: [PATCH] [DRM][KMS][MODE][MEDIATEK] Using the function drm_display_mode_to_videomode

Hi, Satendra: I've applied this patch to my branch mediatek-drm-next-4.18, and I've added below modification in this patch to prevent build error, diff --git a/drivers/gpu/drm/mediatek/Kconfig b/drivers/gpu/drm/mediatek/Kconfig index 294de45..119ec0a 100644 --- a/drivers/gpu/drm/mediatek/Kconfig

[tip:perf/urgent] perf evsel: Only fall back group read for leader

Commit-ID: 121f325f34caf9a7654ec8a50e20942ed9d6dafc Gitweb: https://git.kernel.org/tip/121f325f34caf9a7654ec8a50e20942ed9d6dafc Author: Kan Liang AuthorDate: Tue, 24 Apr 2018 11:20:12 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 24 Apr 2018 16:11:59 -0300 perf evsel: Only

[tip:perf/urgent] perf stat: Print out hint for mixed PMU group error

Commit-ID: 30060eaed769039c6e523b9d159f2b2858fa8907 Gitweb: https://git.kernel.org/tip/30060eaed769039c6e523b9d159f2b2858fa8907 Author: Kan Liang AuthorDate: Tue, 24 Apr 2018 11:20:11 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 24 Apr 2018 16:11:59 -0300 perf stat: Print

[tip:perf/urgent] perf pmu: Fix core PMU alias list for X86 platform

Commit-ID: 292c34c10249c64a70def442f0d977bf9d466ed7 Gitweb: https://git.kernel.org/tip/292c34c10249c64a70def442f0d977bf9d466ed7 Author: Kan Liang AuthorDate: Tue, 24 Apr 2018 11:20:10 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 24 Apr 2018 16:02:29 -0300 perf pmu: Fix co

[tip:perf/urgent] perf record: Fix s390 undefined record__auxtrace_init() return value

Commit-ID: 5d9946c3e5e38e07ab7019db9413a96807a325f2 Gitweb: https://git.kernel.org/tip/5d9946c3e5e38e07ab7019db9413a96807a325f2 Author: Thomas Richter AuthorDate: Mon, 23 Apr 2018 16:29:40 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 12:05:02 -0300 perf record

[tip:perf/urgent] perf evsel: Disable write_backward for leader sampling group events

Commit-ID: e9add8bac6c69edb4bf391e537faa659b2ed70d2 Gitweb: https://git.kernel.org/tip/e9add8bac6c69edb4bf391e537faa659b2ed70d2 Author: Jiri Olsa AuthorDate: Mon, 23 Apr 2018 11:08:19 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 11:21:56 -0300 perf evsel: Disa

[tip:perf/urgent] perf mem: Document incorrect and missing options

Commit-ID: 3138a2ef62667b6ac8eb5fb33a9e0b84ec3ab165 Gitweb: https://git.kernel.org/tip/3138a2ef62667b6ac8eb5fb33a9e0b84ec3ab165 Author: Sangwon Hong AuthorDate: Sun, 22 Apr 2018 16:29:06 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 11:59:18 -0300 perf mem: Doc

[PATCH 4/4] tty: n_gsm: Fix the test for if DLCI0 is open

Logically, if gsm->dlci[0] is NULL then it's not open. Also if it's NULL then we would Oops when we do dlci_get(gsm->dlci[0]); at the end of the function. Reported-by: Sun Peng Signed-off-by: Dan Carpenter diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c index 44e9c5e3dbc1..660153538ca7

[tip:perf/urgent] perf pmu: Fix pmu events parsing rule

Commit-ID: 9a4a931ce847f4aaa12edf11b2e050e18bf45910 Gitweb: https://git.kernel.org/tip/9a4a931ce847f4aaa12edf11b2e050e18bf45910 Author: Jiri Olsa AuthorDate: Mon, 23 Apr 2018 11:08:18 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 11:17:27 -0300 perf pmu: Fix pm

[tip:perf/urgent] perf stat: Keep the / modifier separator in fallback

Commit-ID: 129193bb0c43d42f1c397c175346e3e0dba5a578 Gitweb: https://git.kernel.org/tip/129193bb0c43d42f1c397c175346e3e0dba5a578 Author: Jiri Olsa AuthorDate: Mon, 23 Apr 2018 11:08:17 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 11:14:10 -0300 perf stat: Keep

[PATCH 3/4] tty: n_gsm: Remove an unused lock

We don't use this spin_lock so we can remove the dead code. Signed-off-by: Dan Carpenter diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c index 1f2fd9e76fe0..44e9c5e3dbc1 100644 --- a/drivers/tty/n_gsm.c +++ b/drivers/tty/n_gsm.c @@ -177,7 +177,6 @@ struct gsm_control { struct gsm_mux {

[PATCH 2/4] tty: n_gsm: Prevent a potential use after free

We're freeing the gsm->dlci[] array elements but leaving the freed pointers hanging around. My concern here is if we use the ioctl to change the config, it triggers a restart in gsmld_config(). In that case, we would only reset the first ->dlci[0] element and not the others so it does look to me

[PATCH 1/4] tty: n_gsm: add some locking around gsm_mux[]

We should take "gsm_mux_lock" when we access gsm_mux[]. Reported-by: Sun Peng Signed-off-by: Dan Carpenter diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c index 3b3e1f6632d7..cc7f68814200 100644 --- a/drivers/tty/n_gsm.c +++ b/drivers/tty/n_gsm.c @@ -2898,18 +2898,22 @@ static int gsmtty

Re: [PATCH 8/9] mtd: nand: qcom: helper function for raw read

On 2018-04-25 18:29, Miquel Raynal wrote: Hi Abhishek, On Wed, 25 Apr 2018 12:02:29 +0530, Abhishek Sahu wrote: On 2018-04-23 12:28, Miquel Raynal wrote: > Hi Abhishek, > > On Mon, 23 Apr 2018 11:58:42 +0530, Abhishek Sahu > wrote: > >> On 2018-04-22 21:49, Miquel Raynal wrote: >> > Hi Abhis

[tip:perf/urgent] perf test: Adapt test case record+probe_libc_inet_pton.sh for s390

Commit-ID: b31a8cc1a53dda3a33b6c9c62779869d4d5fc142 Gitweb: https://git.kernel.org/tip/b31a8cc1a53dda3a33b6c9c62779869d4d5fc142 Author: Thomas Richter AuthorDate: Mon, 23 Apr 2018 10:24:28 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 11:04:37 -0300 perf test:

[tip:perf/urgent] perf list: Remove s390 specific strcmp_cpuid_cmp function

Commit-ID: ce04abfbd3ea545a8eb38a8b6a48fb6e7d139dcb Gitweb: https://git.kernel.org/tip/ce04abfbd3ea545a8eb38a8b6a48fb6e7d139dcb Author: Thomas Richter AuthorDate: Mon, 23 Apr 2018 10:17:45 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 11:03:13 -0300 perf list:

[tip:perf/urgent] perf machine: Set main kernel end address properly

Commit-ID: ee05d21791db6db954bbb7b79bb18d88b5f6b7ff Gitweb: https://git.kernel.org/tip/ee05d21791db6db954bbb7b79bb18d88b5f6b7ff Author: Namhyung Kim AuthorDate: Mon, 19 Feb 2018 19:05:45 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 23 Apr 2018 10:52:55 -0300 perf machine:

Re: [PATCH] i2c: at91: Read all available bytes at once

Hi Ludovic, Am 25.04.2018 um 17:08 schrieb Ludovic Desroches: Hi David, On Wed, Apr 18, 2018 at 02:40:55PM +0200, David Engraf wrote: With FIFO enabled it is possible to read multiple bytes at once in the interrupt handler as long as RXRDY is set. This may also reduce the number of interrupts.

Re: Linux messages full of `random: get_random_u32 called from`

Hi! > Since Linux 4.17-rcX, Linux spams a lot of `random: get_random_u32 called > from` messages. I believe, this setting should be reverted by default as > otherwise a lot of other messages are not seen. > > Please find my configuration attached. Same here, thinkpad X60: [3.163839] systemd

[PATCH v2] wlcore: sdio: allow pm to handle sdio power

pm_runtime handles sdio power on and power off transitions. An old workaround for trying to control the power explicitly from the driver was in fact causing failures on suspend/resume as the mmc layer already power the module on resume. In case of resume pm_runtime_get sync returns a positive devi

[PATCH] x86/idt: Simplify the idt_setup_apic_and_irq_gates()

The vectors between FIRST_SYSTEM_VECTOR and NR_VECTORS are special IRQ vectors used by the SMP architecture. But, if X86_LOCAL_APIC=n, it will not be used, and the FIRST_SYSTEM_VECTOR is equal to NR_VECTORS. idt_setup_apic_and_irq_gates() didn't notice that, which make the code a little complex.

Re: [PATCH 0/3] K2G: mmc: Update mmc dt node to use sdhci-omap

On Wednesday 25 April 2018 11:10 PM, Santosh Shilimkar wrote: > On 4/25/2018 6:27 AM, Kishon Vijay Abraham I wrote: >> Update mmc dt node to use sdhci-omap binding instead of omap_hsmmc >> binding. >> >> I've also updated keystone_defconfig to enable CONFIG_MMC_SDHCI_OMAP. >> Everyone who use a c

Re: [PATCH] net: phy: marvell: clear wol event before setting it

Hi, On 4/19/2018 5:48 PM, Andrew Lunn wrote: On Thu, Apr 19, 2018 at 04:02:32PM +0800, Jisheng Zhang wrote: From: Jingju Hou If WOL event happened once, the LED[2] interrupt pin will not be cleared unless reading the CSISR register. So clear the WOL event before enabling it. Signed-off-by: J

Re: [PATCH v2] staging: bcm2835-audio: Disconnect and free vchi_instance on module_exit()

Greg deleted your patch already... regards, dan carpenter

Re: [PATCH v2] input/touchscreen: atmel_mxt_ts: Add correct touchpad button mapping for the Caroline Chromebook.

Hello, On 26/04/2018 00:57:34 CEST, Dmitry Torokhov wrote: > On Wed, Apr 25, 2018 at 03:26:50PM -0700, Dmitry Torokhov wrote: >> On Wed, Apr 25, 2018 at 02:32:58PM +0200, Vittorio Gambaletta (VittGam) >> wrote: >> > This patch adds the correct platform data information for the Caroline >> > Chrom

[tip:x86/urgent] x86/vector: Remove the macro VECTOR_OFFSET_START

Commit-ID: e3072805c61167b85a30ceeef606620704db31f7 Gitweb: https://git.kernel.org/tip/e3072805c61167b85a30ceeef606620704db31f7 Author: Dou Liyang AuthorDate: Wed, 25 Apr 2018 10:05:53 +0800 Committer: Ingo Molnar CommitDate: Thu, 26 Apr 2018 07:31:17 +0200 x86/vector: Remove the macro

[tip:x86/urgent] x86/cpufeatures: Enumerate cldemote instruction

Commit-ID: 9124130573950dcfc06b6a59306edfda2fc33ec7 Gitweb: https://git.kernel.org/tip/9124130573950dcfc06b6a59306edfda2fc33ec7 Author: Fenghua Yu AuthorDate: Mon, 23 Apr 2018 11:29:22 -0700 Committer: Ingo Molnar CommitDate: Thu, 26 Apr 2018 07:31:12 +0200 x86/cpufeatures: Enumerate c

Re: issues with suspend on Dell XPS 13 2-in-1

Hi Dennis, On Wed, 2018-04-25 at 22:06 -0500, Dennis Gilmore wrote: > Hi Srinivas, > > Yes I have latest bios, I have version 1.3.1 that was released on > 18th > of  Feb. Can you try these commands and repeat the test? # cd /sys/kernel/debug/pmc_core/ # for i in {0..32}; do echo $i > ltr_ignore;

Re: [GIT PULL 00/12] perf/urgent fixes

erf-urgent-for-mingo-4.17-20180420' of > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/urgent > (2018-04-21 09:38:33 +0200) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > tags/perf-ur

Re: [PATCH] dt-bindings: staging: remove a couple of ADC bindings

@Thomas: Do you guys use this ? On 25-04-18, 20:57, Rob Herring wrote: > Remove LPC32xx and SPEAr ADC bindings in staging. They have not been > touched since 2012. > > Cc: Roland Stigge > Cc: Stefan Roese > Cc: Jonathan Cameron > Cc: Viresh Kumar > Signed-off-by: Rob Herring > --- > Move the

Re: [PATCH V3] cpufreq: powernv: Fix the hardlockup by synchronus smp_call in timer interrupt

* Shilpa Bhat [2018-04-25 16:29:31]: > gpstate_timer_handler() uses synchronous smp_call to set the pstate > on the requested core. This causes the below hard lockup: > > [c03fe566b320] [c01d5340] smp_call_function_single+0x110/0x180 > (unreliable) > [c03fe566b390] [c01d

Re: [PATCH v14 0/9] Address error and recovery for AER and DPC

On 2018-04-23 20:53, Oza Pawandeep wrote: This patch set brings in error handling support for DPC The current implementation of AER and error message broadcasting to the EP driver is tightly coupled and limited to AER service driver. It is important to factor out broadcasting and other link hand

Re: Moving unmaintained filesystems to staging

On Thu, Apr 26, 2018 at 07:58:52AM +0300, Nikolay Borisov wrote: > > > On 25.04.2018 23:30, David Sterba wrote: > > On Wed, Apr 25, 2018 at 08:46:02AM -0700, Matthew Wilcox wrote: > >> Recently ncpfs got moved to staging. Also recently, we had some fuzzer > >> developers report bugs in hfs, whic

Re: [PATCH v1 2/7] serdev: add dev_pm_domain_attach|detach()

On Tue, 2018-04-03 at 12:29 +0200, Marcel Holtmann wrote: > Hi Sean, > > > In order to open up the required power gate before any operation can be > > effectively performed over the serial bus between CPU and serdev, it's > > clearly essential to add common attach functions for PM domains to serde

linux-next: Tree for Apr 26

Hi all, News: There will be no linux-next release tomorrow. Changes since 20180424: The qcom tree gained a build failure so I used the version from next-20180424. The clk-samsung tree gained a build failure so I used the version from next-20180424. The bpf-next tree gained conflicts against th

Re: [PATCH V3] cpufreq: powernv: Fix the hardlockup by synchronus smp_call in timer interrupt

On 25-04-18, 16:29, Shilpasri G Bhat wrote: > gpstate_timer_handler() uses synchronous smp_call to set the pstate > on the requested core. This causes the below hard lockup: > > [c03fe566b320] [c01d5340] smp_call_function_single+0x110/0x180 > (unreliable) > [c03fe566b390] [c00

Re: [RFC 05/10] i2c: s3c2410: Remove support for Exynos5440

Hi Krzysztof, On 25.04.2018 05:32, Krzysztof Kozlowski wrote: The Exynos5440 is not actively developed, there are no development boards available and probably there are no real products with it. Remove wide-tree support for Exynos5440. Signed-off-by: Krzysztof Kozlowski looks good, Reviewed-

Re: Linux messages full of `random: get_random_u32 called from`

> Thanks for the report! > > I assume since you're upgrading your own kernel, you must not be > running Chrome OS on your Acer CB3-431 Chromebook (Edgar). Are you > running Chromium --- or some Linux distribution on it? > > Thanks, > > - Ted Correct, I'm runn

Re: Linux messages full of `random: get_random_u32 called from`

On Wed, Apr 25, 2018 at 09:11:08PM -0700, Sultan Alsawaf wrote: > I noticed "systems without sufficient boot randomness" and would like to add > to this. > > With the changes to /dev/random going from 4.16.3 to 4.16.4, my low-spec > Chromebook does not reach > the login screen upon boot (it stay

Re: Moving unmaintained filesystems to staging

On 25.04.2018 23:30, David Sterba wrote: > On Wed, Apr 25, 2018 at 08:46:02AM -0700, Matthew Wilcox wrote: >> Recently ncpfs got moved to staging. Also recently, we had some fuzzer >> developers report bugs in hfs, which they deem a security hole because >> Ubuntu attempts to automount an insert

Re: [Bug 199473] New: pcieport does not scan devices behind PEX switch, while resources are allocated

lspci -vv loaded in bugzilla. I referred to a pci port nr as the nr in an expansion slot On 25-04-18 19:05, Bjorn Helgaas wrote: [Please retain the mailing list cc when replying] On Wed, Apr 25, 2018 at 3:28 AM Janpieter Sollie wrote: Hi Bjorn, I'm at work now, but I saw your mail contained

Re: linux-next: build failure after merge of the qcom tree

Hi Evan, On Thu, 26 Apr 2018 03:39:25 + Evan Green wrote: > > Guenter and I had a fix for compile test here, which had failures that > looked similar: > > https://lkml.org/lkml/2018/4/18/752 That looks like it could very well be the problem/solution. > I was hoping to verify myself whether

Unable to handle kernel paging request in snd_seq_oss_readq_puts

We report the crash: unable to handle kernel paging request in snd_seq_oss_readq_puts This crash has been found in v4.16 using RaceFuzzer (a modified version of Syzkaller), which we describe more at the end of this report. Our analysis shows that the race occurs when invoking two syscalls concurre

[PATCH] iommu/io-pgtable-arm: Use for_each_set_bit to simplify code

We can use for_each_set_bit() to simplify code slightly in the ARM io-pgtable self tests while unmapping. Signed-off-by: YueHaibing --- drivers/iommu/io-pgtable-arm-v7s.c | 5 + drivers/iommu/io-pgtable-arm.c | 5 + 2 files changed, 2 insertions(+), 8 deletions(-) diff --git a/drive

Re: [RFC 01/10] ARM: dts: exynos: Remove Exynos5440

Hi Krzysztof, On 25.04.2018 05:32, Krzysztof Kozlowski wrote: The Exynos5440 (quad-core A15 with GMAC, PCIe, SATA) was targeting server platforms but it did not make it to the market really. There are no development boards with it and probably there are no real products neither. The developm

[PATCH] md: fix two problems with setting the "re-add" device state.

If "re-add" is written to the "state" file for a device which is faulty, this has an effect similar to removing and re-adding the device. It should take up the same slot in the array that it previously had, and an accelerated (e.g. bitmap-based) rebuild should happen. The slot that "it previousl

Re: [RFC 08/10] spi: s3c64xx: samsung: Remove support for Exynos5440

Hi Krzysztof, On 25.04.2018 05:32, Krzysztof Kozlowski wrote: The Exynos5440 is not actively developed, there are no development boards available and probably there are no real products with it. Remove wide-tree support for Exynos5440. Signed-off-by: Krzysztof Kozlowski Reviewed-by: Andi Shy

Re: [PATCH 05/11] platform: use a dedicated list_head for early devices

Hi Bartosz, I love your patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.17-rc2] [cannot apply to next-20180424] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://githu

Re: Linux messages full of `random: get_random_u32 called from`

I noticed "systems without sufficient boot randomness" and would like to add to this. With the changes to /dev/random going from 4.16.3 to 4.16.4, my low-spec Chromebook does not reach the login screen upon boot (it stays stuck on a black screen) until I provide a source of entropy to the syste

Re: [PATCH v1] kthread/smpboot: Serialize kthread parking against wakeup

On 4/26/2018 1:39 AM, Peter Zijlstra wrote: On Wed, Apr 25, 2018 at 02:03:19PM +0530, Gaurav Kohli wrote: diff --git a/kernel/smpboot.c b/kernel/smpboot.c index 5043e74..c5c5184 100644 --- a/kernel/smpboot.c +++ b/kernel/smpboot.c @@ -122,7 +122,45 @@ static int smpboot_thread_fn(void *data)

Re: [PATCH] IB/rxe: add RXE_START_MASK for rxe_opcode IB_OPCODE_RC_SEND_ONLY_INV

On 2018/4/26 11:52, Jianchao Wang wrote: w/o RXE_START_MASK, the last_psn of IB_OPCODE_RC_SEND_ONLY_INV will not be updated in update_wqe_psn, and the corresponding wqe will not be acked in rxe_completer due to its last_psn is zero. Finally, the other wqe will also not be able to be acked, beca

[PATCH] IB/rxe: add RXE_START_MASK for rxe_opcode IB_OPCODE_RC_SEND_ONLY_INV

w/o RXE_START_MASK, the last_psn of IB_OPCODE_RC_SEND_ONLY_INV will not be updated in update_wqe_psn, and the corresponding wqe will not be acked in rxe_completer due to its last_psn is zero. Finally, the other wqe will also not be able to be acked, because the wqe of IB_OPCODE_RC_SEND_ONLY_INV wit

Re: Affinity for GIC irq line

On 25/04/18 04:23, valmiki wrote: Hi all, When an IRQ line is set affinity using irq_set_affinity, which calls irq_do_set_affinity, this API copies affinity mask to affinity variable in irq_common_data of this irq descriptor. It does a wee bit more. Crucially, it contains the line: re

Re: Linux messages full of `random: get_random_u32 called from`

Dear Theodore, Am 25.04.2018 um 09:41 schrieb Theodore Y. Ts'o: Does this help on your system? Thank you, after figuring out how to apply the paste, yes it helped on my Lenovo X60. commit 4e00b339e264802851aff8e73cde7d24b57b18ce Author: Theodore Ts'o Date: Wed Apr 25 01:12:32 2018 -040

Re: [PATCH 10/11] of: platform: provide of_early_platform_probe()

Hi Bartosz, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17-rc2] [cannot apply to next-20180424] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0d

Re: linux-next: build failure after merge of the rpmsg tree

On Wed 25 Apr 20:33 PDT 2018, Stephen Rothwell wrote: > Hi Bjorn, > > After merging the rpmsg tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/remoteproc/remoteproc_core.c: In function 'rproc_handle_devmem': > drivers/remoteproc/remoteproc_core.c:557:8: err

Re: linux-next: build failure after merge of the qcom tree

On Wed, Apr 25, 2018 at 3:42 PM Stephen Rothwell wrote: > Hi Andy, > After merging the qcom tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > ERROR: "geni_se_select_mode" [drivers/tty/serial/qcom_geni_serial.ko] undefined! > ERROR: "geni_se_init" [drivers/tty/serial/qco

linux-next: build failure after merge of the rpmsg tree

Hi Bjorn, After merging the rpmsg tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/remoteproc/remoteproc_core.c: In function 'rproc_handle_devmem': drivers/remoteproc/remoteproc_core.c:557:8: error: implicit declaration of function 'iommu_map_sync'; did you mean

Re: [PATCH v3 1/3] resource: Use list_head to link sibling resource

Hi Baoquan, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17-rc2 next-20180424] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commit

Re: [PATCH] fault-injection: reorder config entries

On 04/25/2018 01:02 PM, Mikulas Patocka wrote: > This patch reorders Kconfig entries, so that menuconfig displays proper > indentation. > > Signed-off-by: Mikulas Patocka Acked-by: Randy Dunlap Tested-by: Randy Dunlap Thanks. > --- > lib/Kconfig.debug | 36 ++-

Re: [PATCH 8/8] ALSA: add new 32-bit layout for snd_pcm_mmap_status/control

Hi Arnd, I love your patch! Yet something to improve: [auto build test ERROR on v4.17-rc2] [cannot apply to sound/for-next asoc/for-next arm-soc/for-next next-20180424] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

  1   2   3   4   5   6   7   8   9   10   >