Re: general protection fault in blkcipher_walk_done (2)

On Wed, Jan 03, 2018 at 12:58:02AM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 72bca2084a21edda74b802bc076083d5951f67b4 > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console

Re: general protection fault in blkcipher_walk_done (2)

On Wed, Jan 03, 2018 at 12:58:02AM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 72bca2084a21edda74b802bc076083d5951f67b4 > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console

Re: [PATCH v2] dt: psci: Update DT bindings to support hierarchical PSCI states

On Thu, Dec 28, 2017 at 03:40:37PM +0100, Ulf Hansson wrote: > From: Lina Iyer > > Update DT bindings to represent hierarchical CPU and CPU domain idle states > for PSCI. Also update the PSCI examples to clearly show how flattened and > hierarchical idle states can be

Re: [PATCH v2] dt: psci: Update DT bindings to support hierarchical PSCI states

On Thu, Dec 28, 2017 at 03:40:37PM +0100, Ulf Hansson wrote: > From: Lina Iyer > > Update DT bindings to represent hierarchical CPU and CPU domain idle states > for PSCI. Also update the PSCI examples to clearly show how flattened and > hierarchical idle states can be represented in DT. > >

Re: [RESEND PATCH v2 14/15] ASoC: qcom: apq8096: Add db820c machine driver

On 01/03, Srinivas Kandagatla wrote: > Thanks for your review comments, > > On 03/01/18 17:20, Stephen Boyd wrote: > >>+ > >>+ return ret; > >>+} > >>+ > >>+static int msm_snd_apq8096_probe(struct platform_device *pdev) > >>+{ > >>+ int ret; > >>+ struct snd_soc_card *card; > >>+ > >>+

Re: [RESEND PATCH v2 14/15] ASoC: qcom: apq8096: Add db820c machine driver

On 01/03, Srinivas Kandagatla wrote: > Thanks for your review comments, > > On 03/01/18 17:20, Stephen Boyd wrote: > >>+ > >>+ return ret; > >>+} > >>+ > >>+static int msm_snd_apq8096_probe(struct platform_device *pdev) > >>+{ > >>+ int ret; > >>+ struct snd_soc_card *card; > >>+ > >>+

Re: [PATCH] x86/cpu, x86/pti: Do not enable PTI on AMD processors

On 12/26/2017 09:43 PM, Tom Lendacky wrote: >AMD processors are not subject to the types of attacks that the kernel page >table isolation feature protects against. There is no doubt this is a serious flaw. This thread reminded me - about a year ago we discovered a software code that bricked

Re: [PATCH] x86/cpu, x86/pti: Do not enable PTI on AMD processors

On 12/26/2017 09:43 PM, Tom Lendacky wrote: >AMD processors are not subject to the types of attacks that the kernel page >table isolation feature protects against. There is no doubt this is a serious flaw. This thread reminded me - about a year ago we discovered a software code that bricked

Re: [RESEND PATCH v2 07/15] ASoC: qcom: q6asm: Add support to memory map and unmap

On Wed 03 Jan 08:26 PST 2018, Srinivas Kandagatla wrote: > Thanks for your review comments. > > On 02/01/18 05:48, Bjorn Andersson wrote: > > On Thu 14 Dec 09:33 PST 2017, srinivas.kandaga...@linaro.org wrote: [..] > > > +int q6asm_unmap_memory_regions(unsigned int dir, struct audio_client *ac)

Re: [RESEND PATCH v2 07/15] ASoC: qcom: q6asm: Add support to memory map and unmap

On Wed 03 Jan 08:26 PST 2018, Srinivas Kandagatla wrote: > Thanks for your review comments. > > On 02/01/18 05:48, Bjorn Andersson wrote: > > On Thu 14 Dec 09:33 PST 2017, srinivas.kandaga...@linaro.org wrote: [..] > > > +int q6asm_unmap_memory_regions(unsigned int dir, struct audio_client *ac)

Re: [PATCH] tty: fix data race in n_tty_receive_buf_common

On Wed, 3 Jan 2018 19:18:52 +0530 Gaurav Kohli wrote: > There can be a race, if receive_buf call comes before > tty initialization completes in n_tty_open and tty->disc_data > may be NULL. This makes no sense. If the race exists then the check you do isn't good enough

Re: [PATCH] tty: fix data race in n_tty_receive_buf_common

On Wed, 3 Jan 2018 19:18:52 +0530 Gaurav Kohli wrote: > There can be a race, if receive_buf call comes before > tty initialization completes in n_tty_open and tty->disc_data > may be NULL. This makes no sense. If the race exists then the check you do isn't good enough because the ldsic dsta

Re: [PATCH v2 9/9] media: i2c: tw9910: Remove soc_camera dependencies

Hi Fabio, On Wed, Jan 03, 2018 at 04:14:35PM -0200, Fabio Estevam wrote: > On Wed, Jan 3, 2018 at 3:37 PM, jacopo mondi wrote: > > >> Initially the rest GPIO was doing: > >> > >> - gpio_set_value(GPIO_PTT3, 0); > >> - mdelay(10); > >> -

Re: [PATCH v2 9/9] media: i2c: tw9910: Remove soc_camera dependencies

Hi Fabio, On Wed, Jan 03, 2018 at 04:14:35PM -0200, Fabio Estevam wrote: > On Wed, Jan 3, 2018 at 3:37 PM, jacopo mondi wrote: > > >> Initially the rest GPIO was doing: > >> > >> - gpio_set_value(GPIO_PTT3, 0); > >> - mdelay(10); > >> - gpio_set_value(GPIO_PTT3, 1); > >> -

[PATCH v3] ARM: dts: imx6: RDU2: disable internal watchdog

From: Lucas Stach The system has an external watchdog in the environment processor so the internal watchdog is of no use. Cc: Sascha Hauer Cc: Fabio Estevam Cc: Rob Herring Cc: Mark Rutland

[PATCH v3] ARM: dts: imx6: RDU2: disable internal watchdog

From: Lucas Stach The system has an external watchdog in the environment processor so the internal watchdog is of no use. Cc: Sascha Hauer Cc: Fabio Estevam Cc: Rob Herring Cc: Mark Rutland Cc: linux-arm-ker...@lists.infradead.org Cc: devicet...@vger.kernel.org Cc:

Re: bonding: Delete an error message for a failed memory allocation in bond_update_slave_arr()

On Wed, Jan 3, 2018 at 12:45 AM, SF Markus Elfring wrote: >>> Omit an extra message for a memory allocation failure in this function. >>> >>> This issue was detected by using the Coccinelle software. >>> >> What is the issue with this message? > > * Is it redundant?

Re: bonding: Delete an error message for a failed memory allocation in bond_update_slave_arr()

On Wed, Jan 3, 2018 at 12:45 AM, SF Markus Elfring wrote: >>> Omit an extra message for a memory allocation failure in this function. >>> >>> This issue was detected by using the Coccinelle software. >>> >> What is the issue with this message? > > * Is it redundant? > > * Would a Linux allocation

Re: correct section for cpu_tss_rw?

On Tue, 2 Jan 2018, Nick Desaulniers wrote: > (emailing the folks listed from running `./scripts/get_maintainer.pl > -f` on arch/x86/kernel/process.c, arch/x86/include/asm/processor.h, > and include/linux/percpu-defs.h) > > Clang emits the following warning: > > arch/x86/kernel/process.c:50:11:

Re: correct section for cpu_tss_rw?

On Tue, 2 Jan 2018, Nick Desaulniers wrote: > (emailing the folks listed from running `./scripts/get_maintainer.pl > -f` on arch/x86/kernel/process.c, arch/x86/include/asm/processor.h, > and include/linux/percpu-defs.h) > > Clang emits the following warning: > > arch/x86/kernel/process.c:50:11:

Re: CONFIG_PAGE_TABLE_ISOLATION=y on x86_64 causes gcc to segfault when building x86_32 binaries

On Wed, 3 Jan 2018, Thomas Gleixner wrote: > On Wed, 3 Jan 2018, Lars Wendler wrote: > > Am Wed, 3 Jan 2018 13:05:38 +0100 (CET) > > schrieb Thomas Gleixner : > > > Also can you please try Linus v4.15-rc6 with PTI enabled so we can see > > > whether that's a backport issue or

Re: CONFIG_PAGE_TABLE_ISOLATION=y on x86_64 causes gcc to segfault when building x86_32 binaries

On Wed, 3 Jan 2018, Thomas Gleixner wrote: > On Wed, 3 Jan 2018, Lars Wendler wrote: > > Am Wed, 3 Jan 2018 13:05:38 +0100 (CET) > > schrieb Thomas Gleixner : > > > Also can you please try Linus v4.15-rc6 with PTI enabled so we can see > > > whether that's a backport issue or a general one? > >

Re: [PATCH v2 9/9] ASoC: Intel: kconfig: add some comments for if symbols

On 01/03/2018 08:50 AM, Pierre-Louis Bossart wrote: > From: Vinod Koul > > Helps in finding if endings That partial sentence is confusing. I couldn't decode it without reading the entire patch. That shouldn't be necessary. How about: Help in finding (matching) if/endif

Re: [PATCH v2 9/9] ASoC: Intel: kconfig: add some comments for if symbols

On 01/03/2018 08:50 AM, Pierre-Louis Bossart wrote: > From: Vinod Koul > > Helps in finding if endings That partial sentence is confusing. I couldn't decode it without reading the entire patch. That shouldn't be necessary. How about: Help in finding (matching) if/endif pairs. or Help in

page table isolation alternative mechanism

We got into the current situation for performance reasons, avoiding the costly reload of CR3 that a hardware task switch would cause. It seems we'll be loading CR3 now anyway, so it might be time to reconsider hardware task switches. The recent patches leave kernel entry/exit code mapped.

page table isolation alternative mechanism

We got into the current situation for performance reasons, avoiding the costly reload of CR3 that a hardware task switch would cause. It seems we'll be loading CR3 now anyway, so it might be time to reconsider hardware task switches. The recent patches leave kernel entry/exit code mapped.

Re: [PATCH v2 0/9] ASoC: Intel: Kconfig+acpi fixes

On Wed, 2018-01-03 at 12:52 -0600, Pierre-Louis Bossart wrote: > > On 01/03/2018 11:09 AM, Andy Shevchenko wrote: > > On Wed, 2018-01-03 at 10:50 -0600, Pierre-Louis Bossart wrote: > > Couple of nitpicks and seems patch 9 missed some (all?) comments to > > be > > addressed. > > > > So, after

Re: [PATCH v2 0/9] ASoC: Intel: Kconfig+acpi fixes

On Wed, 2018-01-03 at 12:52 -0600, Pierre-Louis Bossart wrote: > > On 01/03/2018 11:09 AM, Andy Shevchenko wrote: > > On Wed, 2018-01-03 at 10:50 -0600, Pierre-Louis Bossart wrote: > > Couple of nitpicks and seems patch 9 missed some (all?) comments to > > be > > addressed. > > > > So, after

Re: [PATCH v5 26/39] nds32: Device tree support

On Tue, Jan 2, 2018 at 2:24 AM, Greentime Hu wrote: > From: Greentime Hu > > This patch adds support for device tree. > > Signed-off-by: Vincent Chen > Signed-off-by: Greentime Hu > --- >

Re: [PATCH v5 26/39] nds32: Device tree support

On Tue, Jan 2, 2018 at 2:24 AM, Greentime Hu wrote: > From: Greentime Hu > > This patch adds support for device tree. > > Signed-off-by: Vincent Chen > Signed-off-by: Greentime Hu > --- > arch/nds32/boot/dts/Makefile |8 + > arch/nds32/boot/dts/ae3xx.dts | 73 >

Re: [PATCH v3] gpio: winbond: add driver

On Sat, 2017-12-30 at 22:02 +0100, Maciej S. Szmigiero wrote: > This commit adds GPIO driver for Winbond Super I/Os. > > Currently, only W83627UHG model (also known as Nuvoton NCT6627UD) is > supported but in the future a support for other Winbond models, too, > can > be added to the driver. > >

Re: [PATCH v3] gpio: winbond: add driver

On Sat, 2017-12-30 at 22:02 +0100, Maciej S. Szmigiero wrote: > This commit adds GPIO driver for Winbond Super I/Os. > > Currently, only W83627UHG model (also known as Nuvoton NCT6627UD) is > supported but in the future a support for other Winbond models, too, > can > be added to the driver. > >

Re: [PATCH] exec: Weaken dumpability for secureexec

On Wed, 3 Jan 2018 09:21:16 -0800 Kees Cook wrote: > The more interesting thing here is that secureexec is set for a > process that ISN'T actually setuid. (ptrace of a setuid process). I > think tha'ts the real bug, but not something I'm going to be able to > fix quickly. So, for now, I want to

Re: [PATCH] exec: Weaken dumpability for secureexec

On Wed, 3 Jan 2018 09:21:16 -0800 Kees Cook wrote: > The more interesting thing here is that secureexec is set for a > process that ISN'T actually setuid. (ptrace of a setuid process). I > think tha'ts the real bug, but not something I'm going to be able to > fix quickly. So, for now, I want to

Re: [f2fs-dev] [PATCH v5] f2fs: add reserved blocks for root user

On 01/03, Chao Yu wrote: > On 2018/1/3 10:21, Jaegeuk Kim wrote: > > This patch allows root to reserve some blocks via mount option. > > > > "-o reserve_root=N" means N x 4KB-sized blocks for root only. > > > > Signed-off-by: Jaegeuk Kim > > --- > > > > Change log from v4:

Re: [f2fs-dev] [PATCH v5] f2fs: add reserved blocks for root user

On 01/03, Chao Yu wrote: > On 2018/1/3 10:21, Jaegeuk Kim wrote: > > This patch allows root to reserve some blocks via mount option. > > > > "-o reserve_root=N" means N x 4KB-sized blocks for root only. > > > > Signed-off-by: Jaegeuk Kim > > --- > > > > Change log from v4: > > - fix f_bfree

Re: WARNING in rds_cmsg_rdma_args

On 1/3/2018 10:51 AM, Mohamed Ghannam wrote: The fix  : https://patchwork.ozlabs.org/patch/854723/ Cool. Thanks Mohamed for following it up. Regards, Santosh

Re: WARNING in rds_cmsg_rdma_args

On 1/3/2018 10:51 AM, Mohamed Ghannam wrote: The fix  : https://patchwork.ozlabs.org/patch/854723/ Cool. Thanks Mohamed for following it up. Regards, Santosh

Re: [PATCH v3] f2fs: add an ioctl to disable GC for specific file

On 01/03, Chao Yu wrote: > On 2018/1/3 11:21, Jaegeuk Kim wrote: > > This patch gives a flag to disable GC on given file, which would be useful, > > when > > user wants to keep its block map. It also conducts in-place-update for > > dontmove > > file. > > > > Signed-off-by: Jaegeuk Kim

Re: [PATCH v3] f2fs: add an ioctl to disable GC for specific file

On 01/03, Chao Yu wrote: > On 2018/1/3 11:21, Jaegeuk Kim wrote: > > This patch gives a flag to disable GC on given file, which would be useful, > > when > > user wants to keep its block map. It also conducts in-place-update for > > dontmove > > file. > > > > Signed-off-by: Jaegeuk Kim > > ---

[PATCH 1/2] f2fs: show precise # of blocks that user/root can use

Let's show precise # of blocks that user/root can use through bavail and bfree respectively. Signed-off-by: Jaegeuk Kim --- fs/f2fs/super.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c index

[PATCH 1/2] f2fs: show precise # of blocks that user/root can use

Let's show precise # of blocks that user/root can use through bavail and bfree respectively. Signed-off-by: Jaegeuk Kim --- fs/f2fs/super.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c index 0a820ba55b10..4c1c99cf54ef 100644 ---

[PATCH 2/2] f2fs: add reserved blocks for root user

This patch allows root to reserve some blocks via mount option. "-o reserve_root=N" means N x 4KB-sized blocks for root only. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 26 ++ fs/f2fs/super.c | 29 ++--- fs/f2fs/sysfs.c

[PATCH 2/2] f2fs: add reserved blocks for root user

This patch allows root to reserve some blocks via mount option. "-o reserve_root=N" means N x 4KB-sized blocks for root only. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 26 ++ fs/f2fs/super.c | 29 ++--- fs/f2fs/sysfs.c | 3 ++- 3 files

[PATCH -mm] proc: fixup comment

Document what ->pde_unload_lock actually does. Signed-off-by: Alexey Dobriyan --- fs/proc/internal.h |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --- a/fs/proc/internal.h +++ b/fs/proc/internal.h @@ -38,7 +38,8 @@ struct proc_dir_entry { atomic_t

[PATCH -mm] proc: fixup comment

Document what ->pde_unload_lock actually does. Signed-off-by: Alexey Dobriyan --- fs/proc/internal.h |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --- a/fs/proc/internal.h +++ b/fs/proc/internal.h @@ -38,7 +38,8 @@ struct proc_dir_entry { atomic_t in_use; atomic_t

Re: KASAN: slab-out-of-bounds Write in tcp_v6_syn_recv_sock

On Tue, Jan 2, 2018 at 3:58 PM, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 61233580f1f33c50e159c50e24d80ffd2ba2e06b > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master > compiler: gcc (GCC) 7.1.1

Re: KASAN: slab-out-of-bounds Write in tcp_v6_syn_recv_sock

On Tue, Jan 2, 2018 at 3:58 PM, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 61233580f1f33c50e159c50e24d80ffd2ba2e06b > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console output is

Re: [PATCH v2 0/9] ASoC: Intel: Kconfig+acpi fixes

On 01/03/2018 11:09 AM, Andy Shevchenko wrote: On Wed, 2018-01-03 at 10:50 -0600, Pierre-Louis Bossart wrote: The first patch solves issues reported by 0day with non-ACPI platforms The second patch implements what Linus, Takashi and Mark requested: a top-level selector defaulting to 'y' to

Re: [PATCH v2 0/9] ASoC: Intel: Kconfig+acpi fixes

On 01/03/2018 11:09 AM, Andy Shevchenko wrote: On Wed, 2018-01-03 at 10:50 -0600, Pierre-Louis Bossart wrote: The first patch solves issues reported by 0day with non-ACPI platforms The second patch implements what Linus, Takashi and Mark requested: a top-level selector defaulting to 'y' to

Re: general protection fault in fib6_add (2)

On Wed, Jan 3, 2018 at 8:16 AM, David Ahern wrote: > [ +wei...@google.com ] > > On 1/2/18 3:58 PM, syzbot wrote: >> Hello, >> >> syzkaller hit the following crash on >> 61233580f1f33c50e159c50e24d80ffd2ba2e06b >>

Re: general protection fault in fib6_add (2)

On Wed, Jan 3, 2018 at 8:16 AM, David Ahern wrote: > [ +wei...@google.com ] > > On 1/2/18 3:58 PM, syzbot wrote: >> Hello, >> >> syzkaller hit the following crash on >> 61233580f1f33c50e159c50e24d80ffd2ba2e06b >> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master >> compiler:

[PATCH] proc: spread __ro_after_init

/proc/self inode numbers, value of proc_inode_cache and st_nlink of /proc/$TGID are fixed constants. Signed-off-by: Alexey Dobriyan --- fs/proc/base.c|5 +++-- fs/proc/inode.c |3 ++- fs/proc/self.c|3 ++- fs/proc/thread_self.c |3 ++-

[PATCH] proc: spread __ro_after_init

/proc/self inode numbers, value of proc_inode_cache and st_nlink of /proc/$TGID are fixed constants. Signed-off-by: Alexey Dobriyan --- fs/proc/base.c|5 +++-- fs/proc/inode.c |3 ++- fs/proc/self.c|3 ++- fs/proc/thread_self.c |3 ++- 4 files changed, 9

Re: WARNING in rds_cmsg_rdma_args

On 1/3/2018 12:58 AM, syzbot wrote: Hello, syzkaller hit the following crash on ad036b63ee57df9ab802a4eb20cbbbec66aa4520 git://git.cmpxchg.org/linux-mmots.git/master compiler: gcc (GCC) 7.1.1 20170620 .config is attached Raw console output is attached. C reproducer is attached syzkaller

Re: WARNING in rds_cmsg_rdma_args

On 1/3/2018 12:58 AM, syzbot wrote: Hello, syzkaller hit the following crash on ad036b63ee57df9ab802a4eb20cbbbec66aa4520 git://git.cmpxchg.org/linux-mmots.git/master compiler: gcc (GCC) 7.1.1 20170620 .config is attached Raw console output is attached. C reproducer is attached syzkaller

[V3 2/2] ASoC: max98373: Added Amplifier Driver

Signed-off-by: Ryan Lee --- Changes since v2: * Splitted dt bindings to the separated patch * Changed 'interelave-mode' device property from u32 to boolean Changes since v1: * Removed 'codec' from 'max98373_priv' structure :

[V3 2/2] ASoC: max98373: Added Amplifier Driver

Signed-off-by: Ryan Lee --- Changes since v2: * Splitted dt bindings to the separated patch * Changed 'interelave-mode' device property from u32 to boolean Changes since v1: * Removed 'codec' from 'max98373_priv' structure : Now 'max98373_set_clock'

[V3 1/2] dt-bindings: Added device tree binding for max98373 amplifier

Signed-off-by: Ryan Lee --- Changes since v2: * Splitted dt bindings to the separated patch * Changed 'interelave-mode' device property from u32 to boolean .../devicetree/bindings/sound/max98373.txt | 40 ++ 1 file

[V3 1/2] dt-bindings: Added device tree binding for max98373 amplifier

Signed-off-by: Ryan Lee --- Changes since v2: * Splitted dt bindings to the separated patch * Changed 'interelave-mode' device property from u32 to boolean .../devicetree/bindings/sound/max98373.txt | 40 ++ 1 file changed, 40 insertions(+) create

RE: [v2] ASoC: max98373: Added Amplifier Driver

>-Original Message- >From: Rob Herring [mailto:r...@kernel.org] >Sent: Tuesday, December 26, 2017 3:33 PM >To: Ryan Lee >Cc: lgirdw...@gmail.com; broo...@kernel.org; mark.rutl...@arm.com; >pe...@perex.cz; ti...@suse.com; a...@arndb.de; a...@ti.com;

RE: [v2] ASoC: max98373: Added Amplifier Driver

>-Original Message- >From: Rob Herring [mailto:r...@kernel.org] >Sent: Tuesday, December 26, 2017 3:33 PM >To: Ryan Lee >Cc: lgirdw...@gmail.com; broo...@kernel.org; mark.rutl...@arm.com; >pe...@perex.cz; ti...@suse.com; a...@arndb.de; a...@ti.com; >robert.jarz...@free.fr;

Re: [RESEND PATCH v2 14/15] ASoC: qcom: apq8096: Add db820c machine driver

Thanks for your review comments, On 03/01/18 17:20, Stephen Boyd wrote: On 12/14/2017 09:34 AM, srinivas.kandaga...@linaro.org wrote: From: Srinivas Kandagatla diff --git a/sound/soc/qcom/apq8096.c b/sound/soc/qcom/apq8096.c new file mode 100644 index

Re: [RESEND PATCH v2 14/15] ASoC: qcom: apq8096: Add db820c machine driver

Thanks for your review comments, On 03/01/18 17:20, Stephen Boyd wrote: On 12/14/2017 09:34 AM, srinivas.kandaga...@linaro.org wrote: From: Srinivas Kandagatla diff --git a/sound/soc/qcom/apq8096.c b/sound/soc/qcom/apq8096.c new file mode 100644 index ..5b2036317f71 ---

Re: perf test BPF failing on 4.15.0-rc6

Em Wed, Jan 03, 2018 at 03:27:01PM -0300, Arnaldo Carvalho de Melo escreveu: > > Continuing investigation... > > After applying the fallback patch to allow new tools to work with older > kernels: > > [root@felicio ~]# perf test bpf > 39: BPF filter: >

Re: perf test BPF failing on 4.15.0-rc6

Em Wed, Jan 03, 2018 at 03:27:01PM -0300, Arnaldo Carvalho de Melo escreveu: > > Continuing investigation... > > After applying the fallback patch to allow new tools to work with older > kernels: > > [root@felicio ~]# perf test bpf > 39: BPF filter: >

Re: perf test BPF failing on 4.15.0-rc6

Em Wed, Jan 03, 2018 at 01:58:44PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Wed, Jan 03, 2018 at 12:58:26PM +0800, Wangnan (F) escreveu: > > And please check if the kprobe created by > > > > $ perf probe -v SyS_epoll_wait > > [root@seventh ~]# perf probe -v SyS_epoll_wait >

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

> Sorry, I find this very confusing. > > It seems we have some people telling me that when there's no PHY described > in DT, we use this link interrupt, and have a functional network interface > (presumably at whatever speed.) I give you couple of examples when we have functional network

Re: perf test BPF failing on 4.15.0-rc6

Em Wed, Jan 03, 2018 at 01:58:44PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Wed, Jan 03, 2018 at 12:58:26PM +0800, Wangnan (F) escreveu: > > And please check if the kprobe created by > > > > $ perf probe -v SyS_epoll_wait > > [root@seventh ~]# perf probe -v SyS_epoll_wait >

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

> Sorry, I find this very confusing. > > It seems we have some people telling me that when there's no PHY described > in DT, we use this link interrupt, and have a functional network interface > (presumably at whatever speed.) I give you couple of examples when we have functional network

Re: [PATCH 04/12] PCI: qcom: account for const type of of_device_id.data

On Wed, Jan 03, 2018 at 01:38:27PM +0100, Julia Lawall wrote: > > > On Wed, 3 Jan 2018, Lorenzo Pieralisi wrote: > > > On Tue, Jan 02, 2018 at 02:28:00PM +0100, Julia Lawall wrote: > > > This driver creates various const structures that it stores in the > > > data field of an of_device_id

Re: [PATCH 04/12] PCI: qcom: account for const type of of_device_id.data

On Wed, Jan 03, 2018 at 01:38:27PM +0100, Julia Lawall wrote: > > > On Wed, 3 Jan 2018, Lorenzo Pieralisi wrote: > > > On Tue, Jan 02, 2018 at 02:28:00PM +0100, Julia Lawall wrote: > > > This driver creates various const structures that it stores in the > > > data field of an of_device_id

Re: [PATCH] irqchip/gic-v3-its: Add workaround for ThunderX2 erratum #174

On 03/01/18 18:13, Ganapatrao Kulkarni wrote: > On Wed, Jan 3, 2018 at 5:06 PM, Marc Zyngier wrote: >> On 03/01/18 11:20, Ganapatrao Kulkarni wrote: >>> On Wed, Jan 3, 2018 at 3:43 PM, Marc Zyngier wrote: On 03/01/18 09:35, Ganapatrao Kulkarni

Re: [PATCH] irqchip/gic-v3-its: Add workaround for ThunderX2 erratum #174

On 03/01/18 18:13, Ganapatrao Kulkarni wrote: > On Wed, Jan 3, 2018 at 5:06 PM, Marc Zyngier wrote: >> On 03/01/18 11:20, Ganapatrao Kulkarni wrote: >>> On Wed, Jan 3, 2018 at 3:43 PM, Marc Zyngier wrote: On 03/01/18 09:35, Ganapatrao Kulkarni wrote: > Hi Marc, > > On Wed, Jan

[PATCH] tty: n_gsm: Allow ADM response in addition to UA for control dlci

Some devices have the control dlci stay in ADM mode instead of the UA mode. This can seen at least on droid 4 when trying to open the ts 27.010 mux port. Enabling n_gsm debug mode shows the control dlci always respond with DM to SABM instead of UA: # modprobe n_gsm debug=0xff # ldattach -d

[PATCH] tty: n_gsm: Allow ADM response in addition to UA for control dlci

Some devices have the control dlci stay in ADM mode instead of the UA mode. This can seen at least on droid 4 when trying to open the ts 27.010 mux port. Enabling n_gsm debug mode shows the control dlci always respond with DM to SABM instead of UA: # modprobe n_gsm debug=0xff # ldattach -d

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

Russell, 2018-01-03 18:54 GMT+01:00 Russell King - ARM Linux : > On Wed, Jan 03, 2018 at 05:00:47PM +, Stefan Chulski wrote: >> > > > -Original Message- >> > > > Hi Russell, >> > > > >> > > > Indeed. RGMII MAC behaves same way, although it shouldn't be named >>

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

Russell, 2018-01-03 18:54 GMT+01:00 Russell King - ARM Linux : > On Wed, Jan 03, 2018 at 05:00:47PM +, Stefan Chulski wrote: >> > > > -Original Message- >> > > > Hi Russell, >> > > > >> > > > Indeed. RGMII MAC behaves same way, although it shouldn't be named >> > > > as 'in- band' to

Re: [PATCH v2 9/9] media: i2c: tw9910: Remove soc_camera dependencies

On Wed, Jan 3, 2018 at 3:37 PM, jacopo mondi wrote: >> Initially the rest GPIO was doing: >> >> - gpio_set_value(GPIO_PTT3, 0); >> - mdelay(10); >> - gpio_set_value(GPIO_PTT3, 1); >> - mdelay(10); /* wait to let chip come out of reset */ > > And that's

Re: [PATCH v2 9/9] media: i2c: tw9910: Remove soc_camera dependencies

On Wed, Jan 3, 2018 at 3:37 PM, jacopo mondi wrote: >> Initially the rest GPIO was doing: >> >> - gpio_set_value(GPIO_PTT3, 0); >> - mdelay(10); >> - gpio_set_value(GPIO_PTT3, 1); >> - mdelay(10); /* wait to let chip come out of reset */ > > And that's what my driver code

Re: [PATCH] irqchip/gic-v3-its: Add workaround for ThunderX2 erratum #174

On Wed, Jan 3, 2018 at 5:06 PM, Marc Zyngier wrote: > On 03/01/18 11:20, Ganapatrao Kulkarni wrote: >> On Wed, Jan 3, 2018 at 3:43 PM, Marc Zyngier wrote: >>> On 03/01/18 09:35, Ganapatrao Kulkarni wrote: Hi Marc, On Wed, Jan 3, 2018 at

Re: [PATCH] irqchip/gic-v3-its: Add workaround for ThunderX2 erratum #174

On Wed, Jan 3, 2018 at 5:06 PM, Marc Zyngier wrote: > On 03/01/18 11:20, Ganapatrao Kulkarni wrote: >> On Wed, Jan 3, 2018 at 3:43 PM, Marc Zyngier wrote: >>> On 03/01/18 09:35, Ganapatrao Kulkarni wrote: Hi Marc, On Wed, Jan 3, 2018 at 2:17 PM, Marc Zyngier wrote: > On

Re: [PATCH v2 5/9] ASoC: Intel: Fix nested/unnecessary Kconfig dependencies

On Wed, 2018-01-03 at 10:50 -0600, Pierre-Louis Bossart wrote: > This patch fixes a number of issues: > 1. IOSF_MBI is only needed for byt-cr detection, which is only > supported > on Baytrail/Cherrytrail, move to HiFi2 config > > tristate "Intel ASoC SST driver for ACPI HiFi2 platforms >

Re: [PATCH v2 5/9] ASoC: Intel: Fix nested/unnecessary Kconfig dependencies

On Wed, 2018-01-03 at 10:50 -0600, Pierre-Louis Bossart wrote: > This patch fixes a number of issues: > 1. IOSF_MBI is only needed for byt-cr detection, which is only > supported > on Baytrail/Cherrytrail, move to HiFi2 config > > tristate "Intel ASoC SST driver for ACPI HiFi2 platforms >

Re: [GIT PULL rcu/next] RCU commits for 4.15

On Wed, Jan 03, 2018 at 02:17:17PM +0100, Ingo Molnar wrote: > > * Paul E. McKenney wrote: [ . . . ] > Assuming that the subject line wanted to say v4.16, not v4.15 (which would be > really scary set of changes so late in the v4.15 cycle), I have pulled these >

Re: [GIT PULL rcu/next] RCU commits for 4.15

On Wed, Jan 03, 2018 at 02:17:17PM +0100, Ingo Molnar wrote: > > * Paul E. McKenney wrote: [ . . . ] > Assuming that the subject line wanted to say v4.16, not v4.15 (which would be > really scary set of changes so late in the v4.15 cycle), I have pulled these > into > tip:core/rcu, thanks

[PATCH v9 8/8] ntb: ntb_hw_switchtec: Cleanup 64bit IO defines to use the common header

Clean up the ifdefs which conditionally defined the io{read|write}64 functions in favour of the new common io-64-nonatomic-lo-hi header. Signed-off-by: Logan Gunthorpe Cc: Jon Mason --- drivers/ntb/hw/mscc/ntb_hw_switchtec.c | 30

[PATCH v9 8/8] ntb: ntb_hw_switchtec: Cleanup 64bit IO defines to use the common header

Clean up the ifdefs which conditionally defined the io{read|write}64 functions in favour of the new common io-64-nonatomic-lo-hi header. Signed-off-by: Logan Gunthorpe Cc: Jon Mason --- drivers/ntb/hw/mscc/ntb_hw_switchtec.c | 30 +- 1 file changed, 1 insertion(+),

[PATCH v9 4/8] iomap: introduce io{read|write}64_{lo_hi|hi_lo}

In order to provide non-atomic functions for io{read|write}64 that will use readq and writeq when appropriate. We define a number of variants of these functions in the generic iomap that will do non-atomic operations on pio but atomic operations on mmio. These functions are only defined if readq

[PATCH v9 4/8] iomap: introduce io{read|write}64_{lo_hi|hi_lo}

In order to provide non-atomic functions for io{read|write}64 that will use readq and writeq when appropriate. We define a number of variants of these functions in the generic iomap that will do non-atomic operations on pio but atomic operations on mmio. These functions are only defined if readq

[PATCH v9 2/8] powerpc: io.h: move iomap.h include so that it can use readq/writeq defs

Subsequent patches in this series makes use of the readq and writeq defines in iomap.h. However, as is, they get missed on the powerpc platform seeing the include comes before the define. This patch moves the include down to fix this. Signed-off-by: Logan Gunthorpe Acked-by:

[PATCH v9 2/8] powerpc: io.h: move iomap.h include so that it can use readq/writeq defs

Subsequent patches in this series makes use of the readq and writeq defines in iomap.h. However, as is, they get missed on the powerpc platform seeing the include comes before the define. This patch moves the include down to fix this. Signed-off-by: Logan Gunthorpe Acked-by: Michael Ellerman

Re: [PATCH net-next v2 4/4] net: mvpp2: 2500baseX support

Hi Andrew, On Wed, Jan 03, 2018 at 04:53:11PM +0100, Andrew Lunn wrote: > On Wed, Jan 03, 2018 at 04:32:27PM +0100, Antoine Tenart wrote: > > On Wed, Jan 03, 2018 at 04:20:36PM +0100, Andrew Lunn wrote: > > > > @@ -4612,6 +4616,9 @@ static int mvpp22_comphy_init(struct mvpp2_port > > > > *port)

Re: [PATCH net-next v2 4/4] net: mvpp2: 2500baseX support

Hi Andrew, On Wed, Jan 03, 2018 at 04:53:11PM +0100, Andrew Lunn wrote: > On Wed, Jan 03, 2018 at 04:32:27PM +0100, Antoine Tenart wrote: > > On Wed, Jan 03, 2018 at 04:20:36PM +0100, Andrew Lunn wrote: > > > > @@ -4612,6 +4616,9 @@ static int mvpp22_comphy_init(struct mvpp2_port > > > > *port)

[PATCH v9 5/8] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros

This patch adds generic io{read|write}64[be]{_lo_hi|_hi_lo} macros if they are not already defined by the architecture. (As they are provided by the generic iomap library). The patch also points io{read|write}64[be] to the variant specified by the header name. This is because new drivers are

[PATCH v9 5/8] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros

This patch adds generic io{read|write}64[be]{_lo_hi|_hi_lo} macros if they are not already defined by the architecture. (As they are provided by the generic iomap library). The patch also points io{read|write}64[be] to the variant specified by the header name. This is because new drivers are

[PATCH v9 6/8] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks

Now that ioread64 and iowrite64 are available in io-64-nonatomic, we can remove the hack at the top of ntb_hw_intel.c and replace it with an include. Signed-off-by: Logan Gunthorpe Reviewed-by: Andy Shevchenko Acked-by: Dave Jiang

[PATCH v9 3/8] powerpc: iomap.c: introduce io{read|write}64_{lo_hi|hi_lo}

These functions will be introduced into the generic iomap.c so they can deal with PIO accesses in hi-lo/lo-hi variants. Thus, the powerpc version of iomap.c will need to provide the same functions even though, in this arch, they are identical to the regular io{read|write}64 functions.

[PATCH v9 6/8] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks

Now that ioread64 and iowrite64 are available in io-64-nonatomic, we can remove the hack at the top of ntb_hw_intel.c and replace it with an include. Signed-off-by: Logan Gunthorpe Reviewed-by: Andy Shevchenko Acked-by: Dave Jiang Acked-by: Allen Hubbe Acked-by: Jon Mason # Please enter the

[PATCH v9 3/8] powerpc: iomap.c: introduce io{read|write}64_{lo_hi|hi_lo}

These functions will be introduced into the generic iomap.c so they can deal with PIO accesses in hi-lo/lo-hi variants. Thus, the powerpc version of iomap.c will need to provide the same functions even though, in this arch, they are identical to the regular io{read|write}64 functions.

<    5   6   7   8   9   10   11   12   13   14   >