RE: [PATCH 1/2] thermal: imx: improve error message

Gentle ping this patch set Anson Huang Best Regards! > -Original Message- > From: Daniel Lezcano > Sent: Thursday, September 13, 2018 9:43 PM > To: Anson Huang ; rui.zh...@intel.com; > edubez...@gmail.com; linux...@vger.kernel.org; > linux-kernel@vger.kernel.org > Subject: Re: [PATC

RE: [PATCH v3 1/2] mtd: spi-nor: add macros related to MICRON flash

Hi Boris, > -Original Message- > From: Boris Brezillon [mailto:boris.brezil...@bootlin.com] > Sent: Friday, October 12, 2018 11:38 AM > To: Yogesh Narayan Gaur > Cc: linux-...@lists.infradead.org; linux-...@vger.kernel.org; > tudor.amba...@microchip.com; marek.va...@gmail.com; > cyrille.p

Re: [PATCH 1/6] mm: get_user_pages: consolidate error handling

On Thu, Oct 11, 2018 at 11:00:09PM -0700, john.hubb...@gmail.com wrote: > From: John Hubbard > > An upcoming patch requires a way to operate on each page that > any of the get_user_pages_*() variants returns. > > In preparation for that, consolidate the error handling for > __get_user_pages(). T

Re: [PATCH 4.4 00/27] 4.4.161-stable review

On Thu, Oct 11, 2018 at 03:22:11PM -0700, kernelci.org bot wrote: > > > Full Boot Summary: > https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.160-28-gb3522afcec59/ > Full Build Summary: > https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.160-28-gb3522

[PATCH] gpiolib: Initialize gdev field before is used

gpio_hog depends on gdev field being initialized. This patch fixes an OOPs during initialization of TI's AM335x-ICEv2. Fixes: 3edfb7bd76bd1cba ("gpiolib: Show correct direction from the beginning") Tested-by: Vignesh R Signed-off-by: Ricardo Ribalda Delgado --- drivers/gpio/gpiolib.c | 5 +++--

Re: [PATCH] ALSA: hda - Add mic quirk for the Lenovo G50-30 (17aa:3905)

On Thu, 11 Oct 2018 21:49:17 +0200, Jeremy Cline wrote: > > The Lenovo G50-30, like other G50 models, has a Conexant codec that > requires a quirk for its inverted stereo dmic. > > Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1249364 > Reported-by: Alexander Ploumistos > Tested-by: Alex

Re: [PATCH v3 1/2] mtd: spi-nor: add macros related to MICRON flash

On Fri, 12 Oct 2018 02:23:08 + Yogesh Narayan Gaur wrote: > Some MICRON related macros in spi-nor domain were ST. > Rename entries related to STMicroelectronics under macro SNOR_MFR_ST. > > Added entry of MFR Id for Micron flashes, 0x002C. > > Signed-off-by: Yogesh Gaur > Reviewed-by: Tudo

Re: [PATCH v5 3/3] gpiolib: Show correct direction from the beginning

On Fri, Oct 12, 2018 at 7:59 AM Vignesh R wrote: > On Thursday 11 October 2018 07:12 PM, Ricardo Ribalda Delgado wrote: > > Hi Vignesh > > > > Ups, it does not look too good :S . Can you check if this change fixes it: > > > > Below diff works for me. I no longer see crash and gpio-hog seems to be

Re: [PATCH 4/7] mfd: ds90ux9xx: add TI DS90Ux9xx de-/serializer MFD driver

On Tue, 09 Oct 2018, Vladimir Zapolskiy wrote: > From: Vladimir Zapolskiy > > The change adds I2C device driver for TI DS90Ux9xx de-/serializers, > support of subdevice controllers is done in separate drivers, because > not all IC functionality may be needed in particular situations, and > this

[PATCH 5/6] mm: introduce zone_gup_lock, for dma-pinned pages

From: John Hubbard The page->dma_pinned_flags and _count fields require lock protection. A lock at approximately the granularity of the zone_lru_lock is called for, but adding to the locking contention of zone_lru_lock is undesirable, because that is a pre-existing hot spot. Fortunately, these ne

[PATCH 1/6] mm: get_user_pages: consolidate error handling

From: John Hubbard An upcoming patch requires a way to operate on each page that any of the get_user_pages_*() variants returns. In preparation for that, consolidate the error handling for __get_user_pages(). This provides a single location (the "out:" label) for operating on the collected set o

[PATCH 2/6] mm: introduce put_user_page*(), placeholder versions

From: John Hubbard Introduces put_user_page(), which simply calls put_page(). This provides a way to update all get_user_pages*() callers, so that they call put_user_page(), instead of put_page(). Also introduces put_user_pages(), and a few dirty/locked variations, as a replacement for release_p

[PATCH 4/6] mm: introduce page->dma_pinned_flags, _count

From: John Hubbard Add two struct page fields that, combined, are unioned with struct page->lru. There is no change in the size of struct page. These new fields are for type safety and clarity. Also add page flag accessors to test, set and clear the new page->dma_pinned_flags field. The page->d

[PATCH 3/6] infiniband/mm: convert put_page() to put_user_page*()

From: John Hubbard For infiniband code that retains pages via get_user_pages*(), release those pages via the new put_user_page(), or put_user_pages*(), instead of put_page() This is a tiny part of the second step of fixing the problem described in [1]. The steps are: 1) Provide put_user_page*()

[PATCH 6/6] mm: track gup pages with page->dma_pinned_* fields

From: John Hubbard This patch sets and restores the new page->dma_pinned_flags and page->dma_pinned_count fields, but does not actually use them for anything yet. In order to use these fields at all, the page must be removed from any LRU list that it's on. The patch also adds some precautions th

[PATCH 0/6] RFC: gup+dma: tracking dma-pinned pages

From: John Hubbard Here is an updated proposal for tracking pages that have had get_user_pages*() called on them. This is in support of fixing the problem discussed in [1]. This RFC only shows how to set up a reliable PageDmaPinned flag. What to *do* with that flag is left for a later discussion.

Re: [PATCH v5 3/3] gpiolib: Show correct direction from the beginning

On Friday 05 October 2018 12:23 PM, Ricardo Ribalda Delgado wrote: >>> Current code assumes that the direction is input if direction_input >>> function is set. >>> This might not be the case on GPIOs with programmable direction. >>> >>> Signed-off-by:

Re: [PATCH v1] phy: qcom-qusb2: Fix HSTX_TRIM tuning with fused value for SDM845

Hi, On 2018-10-11 04:06, Doug Anderson wrote: Hi, On Fri, Oct 5, 2018 at 2:09 AM Manu Gautam wrote: Tune1 register on sdm845 is used to update HSTX_TRIM with fused setting. Enable same by specifying update_tune1_with_efuse flag for sdm845, otherwise driver ends up programming tune2 register

linux-next: manual merge of the xarray tree with the nnvdimm-fixes tree

Hi all, Today's linux-next merge of the xarray tree got a conflict in: fs/dax.c between commit: d7782145e1ad ("filesystem-dax: Fix dax_layout_busy_page() livelock") from the nvdimm-fixes tree and commit: 0995344c1493 ("dax: Convert dax_layout_busy_page to XArray") from the xarray tree.

Re: Insanely high baud rates

On 10/11/18 2:40 PM, Theodore Y. Ts'o wrote: > On Thu, Oct 11, 2018 at 07:14:30AM -0700, h...@zytor.com wrote: >>> >>> I mean - what is the baud rate of a pty ? >> >> Whatever the master wants it to be... > > I think Alan's point is that it is highly unlikely you would be able > to push the equiv

[PATCH] perf: Align cpu map events properly.

The size of the resulting cpu map can be smaller than a multiple of sizeof(u64), resulting in SIGBUS on cpus like Sparc as the next event will not be aligned properly. Fixes: 6c872901af07 ("perf cpu_map: Add cpu_map event synthesize function") Signed-off-by: David S. Miller diff --git a/tools/

[PATCH v2] of: base: Change logic in of_alias_get_alias_list()

Check compatible string first before setting up bit in bitmap to also cover cases that allocated bitfield is not big enough. Show warning about it but let driver to continue to work with allocated bitfield to keep at least some devices (included console which is commonly close to serial0) to work.

RE: [PATCH] stm class: increase pos if no free channels found

Hi Alexander, Any comments about this patch? BRs Zhi Jin > -Original Message- > From: Jin, Zhi > Sent: Thursday, September 06, 2018 3:22 PM > To: alexander.shish...@linux.intel.com > Cc: linux-kernel@vger.kernel.org; Jin, Zhi > Subject: [PATCH] stm class: increase pos if no free channel

Re: [PATCH] mm: Speed up mremap on large regions

On Fri, Oct 12, 2018 at 7:29 AM Juergen Gross wrote: > On 12/10/2018 05:21, Jann Horn wrote: > > +cc xen maintainers and kvm folks > > > > On Fri, Oct 12, 2018 at 4:40 AM Joel Fernandes (Google) > > wrote: > >> Android needs to mremap large regions of memory during memory management > >> related

Re: [PATCH] mm: Speed up mremap on large regions

On 12/10/2018 05:21, Jann Horn wrote: > +cc xen maintainers and kvm folks > > On Fri, Oct 12, 2018 at 4:40 AM Joel Fernandes (Google) > wrote: >> Android needs to mremap large regions of memory during memory management >> related operations. The mremap system call can be really slow if THP is >>

linux-next: build warning after merge of the scsi-mkp tree

Hi all, After merging the scsi-mkp tree, today's linux-next build (x86_64 allmodconfig) produced this warning: ./usr/include/scsi/scsi_bsg_ufs.h:45: found __[us]{8,16,32,64} type without #include Introduced by commits a851b2bd3632 ("scsi: uapi: ufs: Make utp_upiu_req visible to user space")

[PATCH V8 15/21] csky: Debug and Ptrace GDB

This patch adds arch ptrace implementation, stack dump and bug.h. Signed-off-by: Guo Ren --- arch/csky/include/asm/bug.h | 26 +++ arch/csky/include/uapi/asm/ptrace.h | 104 arch/csky/kernel/dumpstack.c| 66 arch/csky/kernel/ptrace.c | 314 ++

[PATCH V8 16/21] csky: SMP support

This patch adds boot, ipi, hotplug code for SMP. Changelog: - remove set_ipi_irq_mapping callback. - Convert the cpumask to an interrupt-controller specific representation in driver's code, and not the SMP code's. - csky: remove irq_mapping from smp.c There are some feedbacks from irqchip

[PATCH V8 14/21] csky: User access

This patch adds "user access from kernel" codes. Signed-off-by: Guo Ren --- arch/csky/include/asm/uaccess.h | 416 arch/csky/lib/usercopy.c| 262 + 2 files changed, 678 insertions(+) create mode 100644 arch/csky/include/as

[PATCH V8 12/21] csky: ELF and module probe

This patch adds ELF definition and module relocate codes. Signed-off-by: Guo Ren --- arch/csky/abiv1/inc/abi/elf.h | 26 arch/csky/abiv2/inc/abi/elf.h | 43 arch/csky/include/asm/elf.h | 85 +++ arch/csky/kernel/module.c

[PATCH V8 08/21] csky: Process management and Signal

This patch adds files related to task_switch, sigcontext, signal. Changelog: - abiv2/fpu.c: Userspace should never be sent NSIGXXX as a si_code. Use FPE_FLTUNK instead. - abiv2/fpu.c: Use force_sig_fault instead. Signed-off-by: Guo Ren --- arch/csky/abiv2/fpu.c | 275

[PATCH V8 06/21] csky: Cache and TLB routines

This patch adds cache and tlb sync codes for abiv1 & abiv2. Changelog: - fixup module compile error for EXPORT_SYMBOL(cache_wbinv_range). - tlb.h & cacheflush.h: fix flush_cache_range and tlb_start_vma of abiv1 in flush_cache_range(vma, ...). cache_wbinv_range() couldn't deal with vma->

[PATCH V8 11/21] csky: Atomic operations

This patch adds atomic, cmpxchg, spinlock files. Changlog: - SMP supported - ticklock supported - queue-rwlock supported Signed-off-by: Guo Ren Cc: Peter Zijlstra Cc: Andrea Parri --- arch/csky/include/asm/atomic.h | 212 + arch/csky/include/asm/cmpxchg.h

[PATCH V8 10/21] csky: IRQ handling

This patch adds IRQ handling files. Changelog: - Use CONFIG_GENERIC_IRQ_MULTI_HANDLER Signed-off-by: Guo Ren Cc: Thomas Gleixner --- arch/csky/include/asm/irqflags.h | 49 arch/csky/kernel/irq.c | 22 ++ 2 files changed, 71 in

[PATCH V8 09/21] csky: VDSO and rt_sigreturn

This patch adds files related to VDSO and our VDSO only support rt_sigreturn. Signed-off-by: Guo Ren --- arch/csky/abiv1/inc/abi/vdso.h | 17 + arch/csky/abiv2/inc/abi/vdso.h | 23 +++ arch/csky/include/asm/vdso.h | 12 ++ arch/csky/kernel/vdso.c| 86 +++

[PATCH V8 07/21] csky: MMU and page table management

This patch adds files related to memory management and here is our memory-layout: Fixmap : 0xffc02000 – 0xf000 (4 MB - 12KB) Pkmap: 0xff80 – 0xffc0 (4 MB) Vmalloc : 0xf020 – 0xff00 (238 MB) Lowmem : 0x8000 – 0xc000

[PATCH V8 13/21] csky: Library functions

This patch adds string optimize codes and some auxiliary code. Changelog: - Use bt instead of jbt in asm, jbt will cause relocation problem. - remove kernel/platform.c Signed-off-by: Chen Linfei Signed-off-by: Mao Han Signed-off-by: Guo Ren --- arch/csky/abiv1/bswapdi.c| 12 ++ arc

[PATCH V8 05/21] csky: System Call

This patch adds files related to syscall. Signed-off-by: Guo Ren --- arch/csky/include/asm/syscall.h | 71 + arch/csky/include/asm/syscalls.h| 15 arch/csky/include/uapi/asm/unistd.h | 10 ++ arch/csky/kernel/syscall.c | 43 ++

[PATCH V8 04/21] csky: Exception handling and mm-fault

This patch adds exception handling code, cpuinfo and mm-fault code. Signed-off-by: Guo Ren --- arch/csky/abiv1/alignment.c | 323 arch/csky/abiv1/inc/abi/entry.h | 160 arch/csky/abiv2/inc/abi/entry.h | 156 arch/csky/include

[PATCH V8 03/21] csky: Kernel booting

This patch add boot code. Thx boot params is all in dtb and it's the only way to let kernel get bootloader param information. Changelog: - Use built-in dtb when dtb param is NULL. - Add dummy console for allmodconfig. Signed-off-by: Guo Ren --- arch/csky/kernel/head.S| 77 +++

[PATCH V8 00/21] C-SKY(csky) Linux Kernel Port

This is the 8th version patchset to add the Linux kernel port for C-SKY(csky) based on linux-4.19-rc3. In this patchset, we fixup make allmodconfig and remove one callback in smp.c with irqchip's feedback. Here is the LTP test report for this patchset: (and add "V12 C-SKY(csky) Linux Kernel Drive

[PATCH V8 02/21] csky: defconfig

This patch adds csky defconfig. Signed-off-by: Guo Ren --- arch/csky/configs/defconfig | 61 + 1 file changed, 61 insertions(+) create mode 100644 arch/csky/configs/defconfig diff --git a/arch/csky/configs/defconfig b/arch/csky/configs/defconfig new

[PATCH V8 01/21] csky: Build infrastructure

This patch adds Makefile, Kconfig for build infrastructure. Changelog: - make allmodconfig is OK. - Use BUILTIN_DTB as string, remove bool define for compile. - Add xor.h in asm/Kbuild - Add compat.h in asm/Kbuild. - Add select DMA_DIRECT_OPS in Kconfig. - remove kernel/platform.c in Makefil

Re: [PATCH 4.4 00/27] 4.4.161-stable review

st-vsyscall-mode-native * kselftest-vsyscall-mode-none Summary kernel: 4.4.161-rc1 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git branch: 4.4.161-rc1-hikey-20181011-301 git commit: d3ba9c3a1b2509d2b14941baee1cd504d5ab0a07 git describe: 4.4.161-rc1-hikey-201810

Re: [PATCH 4.9 00/35] 4.9.133-stable review

On Thu, 11 Oct 2018 at 21:14, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.133 release. > There are 35 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Res

Re: [PATCH 4.14 00/45] 4.14.76-stable review

On Thu, 11 Oct 2018 at 21:16, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.76 release. > There are 45 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Res

[PATCH v2 2/2] dt-bindings: uniphier: move cache-uniphier.txt to vendor directory

Now, the Socionext vendor directory is available at Documentation/devicetree/bindings/arm/socionext/ Move cache-uniphier.txt over to it. Signed-off-by: Masahiro Yamada --- Changes in v2: - New patch .../devicetree/bindings/arm/{uniphier => socionext}/cache-uniphier.txt| 0 1 file change

[PATCH v2 1/2] dt-bindings: uniphier: add bindings for UniPhier SoC family

Document the list of SoCs and boards of UniPhier platform. Signed-off-by: Masahiro Yamada --- Changes in v2: Changes suggested by Rob. - Move the file to Documentation/devicetree/bindings/arm/socionext/uniphier.txt - Group boards by each SoC Previous posts: v1: https://patchwork.ozl

Re: [PATCH 4.18 00/44] 4.18.14-stable review

On Thu, 11 Oct 2018 at 21:18, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.18.14 release. > There are 44 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Res

[PATCH V2 4/5] arm64/mm: Enable HugeTLB migration

Let arm64 subscribe to generic HugeTLB page migration framework. Right now this only works on the following PMD and PUD level HugeTLB page sizes with various kernel base page size combinations. CONT PTEPMDCONT PMDPUD ------ 4K: NA 2

[PATCH V2 2/5] mm/hugetlb: Distinguish between migratability and movability

During huge page allocation it's migratability is checked to determine if it should be placed under movable zones with GFP_HIGHUSER_MOVABLE. But the movability aspect of the huge page could depend on other factors than just migratability. Movability in itself is a distinct property which should not

[PATCH V2 3/5] mm/hugetlb: Enable arch specific huge page size support for migration

Architectures like arm64 have HugeTLB page sizes which are different than generic sizes at PMD, PUD, PGD level and implemented via contiguous bits. At present these special size HugeTLB pages cannot be identified through macros like (PMD|PUD|PGDIR)_SHIFT and hence chosen not be migrated. Enabling

[PATCH V2 5/5] arm64/mm: Enable HugeTLB migration for contiguous bit HugeTLB pages

Let arm64 subscribe to the previously added framework in which architecture can inform whether a given huge page size is supported for migration. This just overrides the default function arch_hugetlb_migration_supported() and enables migration for all possible HugeTLB page sizes on arm64. With this

[PATCH V2 0/5] arm64/mm: Enable HugeTLB migration

This patch series enables HugeTLB migration support for all supported huge page sizes at all levels including contiguous bit implementation. Following HugeTLB migration support matrix has been enabled with this patch series. All permutations have been tested except for the 16GB. CONT PTE

[PATCH V2 1/5] mm/hugetlb: Enable PUD level huge page migration

Architectures like arm64 have PUD level HugeTLB pages for certain configs (1GB huge page is PUD based on ARM64_4K_PAGES base page size) that can be enabled for migration. It can be achieved through checking for PUD_SHIFT order based HugeTLB pages during migration. Signed-off-by: Anshuman Khandual

Re: [PATCH v4 2/3] mm: introduce put_user_page*(), placeholder versions

On 10/11/18 6:23 PM, John Hubbard wrote: > On 10/11/18 6:20 AM, Jason Gunthorpe wrote: >> On Thu, Oct 11, 2018 at 10:49:29AM +0200, Jan Kara wrote: >> This is a real worry. If someone uses a mistaken put_page() then how will that bug manifest at runtime? Under what set of circumstances

Re: [PATCH 0/4] Add clock support for Hi3670 SoC

On Thu, Sep 20, 2018 at 11:00:59PM -0700, Manivannan Sadhasivam wrote: > This patchset adds clock support for Hi3670 SoC from HiSilicon utilizing > the HiSi common clock code. While adding clock support, let's remove the > fixed clock for UART and source SoC clock on HiKey970 board. > > This patch

Re: [PATCH] mm: Speed up mremap on large regions

+cc xen maintainers and kvm folks On Fri, Oct 12, 2018 at 4:40 AM Joel Fernandes (Google) wrote: > Android needs to mremap large regions of memory during memory management > related operations. The mremap system call can be really slow if THP is > not enabled. The bottleneck is move_page_tables,

Re: [PATCH V11 1/8] irqchip: add C-SKY SMP interrupt controller

Hi Marc, On Tue, Oct 09, 2018 at 04:11:05PM +0100, Marc Zyngier wrote: > On 09/10/18 15:41, Guo Ren wrote: > > - Irq-csky-mpintc is C-SKY smp system interrupt controller and it > >could support 16 soft irqs, 16 private irqs, and 992 max common > >irqs. > > > >Changelog: > > - Convert the

[PATCH -next] misc: mic: scif: remove set but not used variables 'src_dma_addr, dst_dma_addr'

Fixes gcc '-Wunused-but-set-variable' warning: drivers/misc/mic/scif/scif_dma.c: In function 'scif_rma_list_dma_copy_wrapper': drivers/misc/mic/scif/scif_dma.c:1558:27: warning: variable 'dst_dma_addr' set but not used [-Wunused-but-set-variable] drivers/misc/mic/scif/scif_dma.c:1558:13: warning

Re: [RFC][PATCH] x86: ptrace: Add function argument access API

On Thu, 11 Oct 2018 23:00:21 -0400 Steven Rostedt wrote: > A while ago I posted an RFC patchset for dynamic function based > events. But Masami pointed out that this could be done with kprobes > with minimal changes. He posted a patch set back in March > http://lkml.kernel.org/r/152049860

[RFC][PATCH] x86: ptrace: Add function argument access API

[ A while ago I posted an RFC patchset for dynamic function based events. But Masami pointed out that this could be done with kprobes with minimal changes. He posted a patch set back in March http://lkml.kernel.org/r/152049860385.7289.14079393589900496424.stgit@devbox I've pulled this i

Re: [PATCH] mtd: spi-nor: Add support for SPI boot flash access for AMD Family 16h

Hi Brett, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on mtd/spi-nor/next] [also build test WARNING on v4.19-rc7 next-20181011] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

[for-next][PATCH] trace_uprobe: support reference counter in fd-based uprobe

Added for the 4.20/5.0 queue. -- Steve git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git for-next Head SHA1: a6ca88b241d5e929e6e60b12ad8cd288f0ffa256 Song Liu (1): trace_uprobe: support reference counter in fd-based uprobe include/linux/trace_events.h|

RE: [PATCH v2 2/2] mtd: spi-nor: add entry for mt35xu512aba flash

Hi Tudor, > -Original Message- > From: Tudor Ambarus [mailto:tudor.amba...@microchip.com] > Sent: Thursday, October 11, 2018 9:33 PM > To: Yogesh Narayan Gaur ; linux- > m...@lists.infradead.org; linux-...@vger.kernel.org > Cc: marek.va...@gmail.com; cyrille.pitc...@wedev4u.fr; > boris.bre

[PATCH v3 2/2] mtd: spi-nor: add entry for mt35xu512aba flash

Add entry for mt35xu512aba Micron NOR flash. This flash is having uniform sector erase size of 128KB, have support of FSR(flag status register), flash size is 64MB and supports 4-byte commands. Signed-off-by: Yogesh Gaur Reviewed-by: Tudor Ambarus --- Changes for v3: - Modified flash node style

[PATCH v3 1/2] mtd: spi-nor: add macros related to MICRON flash

Some MICRON related macros in spi-nor domain were ST. Rename entries related to STMicroelectronics under macro SNOR_MFR_ST. Added entry of MFR Id for Micron flashes, 0x002C. Signed-off-by: Yogesh Gaur Reviewed-by: Tudor Ambarus --- Changes for v3: - None Changes for v2: - None drivers/mtd/spi

[PATCH v3 0/2] mtd: spi-nor: add entry for mt35xu512aba flash

Add MFR_ID information, 0x002C, related to the Micron flash. Currently, MFR_ID 0x0020 is being specified as Micron flash ID but these are actually CFI ID of STMicro flashes. Rename SNOR_MFR_MICRON to SNOR_MFR_ST and add entry for SNOR_MFR_MICRON having CFI ID value of Micron flash. Add entry of mt

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

On Thu, Oct 11, 2018 at 7:14 PM, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the tip tree got a conflict in: > > arch/x86/mm/pgtable.c > > between commit: > > 184d47f0fd36 ("x86/mm: Avoid VLA in pgd_alloc()") > > from Linus' tree and commit: > > 1be3f247c288 ("x86/mm: A

Re: [PATCH 1/2] sched/wait: Add wait_event_lock_irq_timeout for TASK_UNINTERRUPTIBLE usage

On 10/9/18 8:23 PM, Nicholas A. Bellinger wrote: Short of reverting commit 00d909a107 for v4.19, target-core needs a wait_event_t marco can be executed using TASK_UNINTERRUPTIBLE to function correctly with existing fabric drivers that expect to run with signals pending during session shutdown and

linux-next: manual merge of the tip tree with Linus' tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: arch/x86/mm/pgtable.c between commit: 184d47f0fd36 ("x86/mm: Avoid VLA in pgd_alloc()") from Linus' tree and commit: 1be3f247c288 ("x86/mm: Avoid VLA in pgd_alloc()") from the tip tree. I fixed it up (I used the versi

Re: [PATCH] KEYS: trusted: fix -Wvarags warning

On Thu, Oct 11, 2018 at 01:31:26PM -0700, ndesaulni...@google.com wrote: > by swapping h2 and h3. > > security/keys/trusted.c:146:17: warning: passing an object that > undergoes default > argument promotion to 'va_start' has undefined behavior [-Wvarargs] > va_start(argp, h3); >

Re: [PATCH] mm: Speed up mremap on large regions

On Thu, Oct 11, 2018 at 11:11:11AM +0300, Kirill A. Shutemov wrote: > On Thu, Oct 11, 2018 at 08:14:19AM +0300, Kirill A. Shutemov wrote: > > On Wed, Oct 10, 2018 at 05:46:18PM -0700, Joel Fernandes wrote: > > > diff --git a/arch/powerpc/include/asm/book3s/64/pgalloc.h > > > b/arch/powerpc/include

Re: [PATCH v15 1/2] leds: core: Introduce LED pattern trigger

Hi, On 12 October 2018 at 04:07, Jacek Anaszewski wrote: > Hi Baolin, > > On 10/11/2018 06:07 AM, Baolin Wang wrote: >> This patch adds a new led trigger that LED device can employ >> software or hardware pattern engine. >> >> Consumers can write 'pattern' file to enable the software pattern >> w

Re: [PATCH v4 2/3] mm: introduce put_user_page*(), placeholder versions

On 10/11/18 6:20 AM, Jason Gunthorpe wrote: > On Thu, Oct 11, 2018 at 10:49:29AM +0200, Jan Kara wrote: > >>> This is a real worry. If someone uses a mistaken put_page() then how >>> will that bug manifest at runtime? Under what set of circumstances >>> will the kernel trigger the bug? >> >> At

Re: [PATCH v2 1/3] namei: implement O_BENEATH-style AT_* flags

On Wed, Oct 10, 2018 at 12:08 AM Aleksa Sarai wrote: > > On 2018-10-09, Andy Lutomirski wrote: > > On Mon, Oct 8, 2018 at 11:53 PM Aleksa Sarai wrote: > > > * AT_NO_PROCLINK: Disallows ->get_link "symlink" jumping. This is a very > > > specific restriction, and it exists because /proc/$pid/fd/

Re: [PATCH v3] ARM: dts: Add support for Liebherr's BK4 device (vf610 based)

On Tue, Oct 09, 2018 at 12:50:28PM +0200, Lukasz Majewski wrote: > This commit adds DTS support for BK4 device from Liebherr. It > uses vf610 SoC from NXP. > > Signed-off-by: Lukasz Majewski As v3 just incorporates a few minor improvements over v2, Stefan's review tag should really be carried.

Re: [PATCH 2/2] clk: add 74aup1g157gw 2-input multiplexer as clock driver

Hi Stephen Thank you for your feedback > > diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig > > index 292056b..9cfeb0e 100644 > > --- a/drivers/clk/Kconfig > > +++ b/drivers/clk/Kconfig > > @@ -299,5 +299,6 @@ source "drivers/clk/sunxi-ng/Kconfig" > > source "drivers/clk/tegra/Kconfig" >

Re: [PATCH v2 1/7] modules: Create rlimit for module space

On Fri, Oct 12, 2018 at 1:40 AM Rick Edgecombe wrote: > This introduces a new rlimit, RLIMIT_MODSPACE, which limits the amount of > module space a user can use. The intention is to be able to limit module space > allocations that may come from un-privlidged users inserting e/BPF filters. Note tha

Re: [PATCH AUTOSEL 4.18 24/58] Input: atakbd - fix Atari CapsLock behaviour

Hi Geert, On Wed, Oct 10, 2018 at 09:04:08PM +0200, Geert Uytterhoeven wrote: > Hi Dmitry, > > On Wed, Oct 10, 2018 at 7:03 PM Dmitry Torokhov > wrote: > > Same goes for patches that deal with error handling in probe() functions > > that your AUTOSEL scripts like to pick. Yes, they are fixing bu

[git pull] Input updates for v4.19-rc7

Hi Greg, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus to receive updates for the input subsystem: - we added a few scheduling points into various input interfaces to ensure that large writes will not cause RCU stalls - fixed configuring PS/

Re: [PATCH] dt-bindings: Add bindings for aliases node

On Mon, Oct 08, 2018 at 10:57:24PM -0700, Stephen Boyd wrote: > Quoting Matthias Kaehlcke (2018-09-25 14:02:55) > > Add a global binding for the 'aliases' node. This includes an initial list > > of standardized alias names for some hardware components that are commonly > > found in 'aliases'. > >

Re: [PATCH v2 4/7] arm64/modules: Add rlimit checking for arm64 modules

On 10/11/2018 04:31 PM, Rick Edgecombe wrote: > + if (check_inc_mod_rlimit(size)) > + return NULL; > + > p = __vmalloc_node_range(size, MODULE_ALIGN, module_alloc_base, > module_alloc_base + MODULES_VSIZE, > gfp_mask,

Re: [PATCH linux-next v3 1/1] ASoC: rsnd: ssi: Request dedicated dma channels for busif0 to 7

Hi > Currently ssi driver only requests dma channel for SSI_0, with > naming of 'rxu/txu', which is used to transfer data to/from busif0. > But for GEN2/GEN3, there are also busif1 ~ busif7, which need to > be used when SSI works in TDM Split/Ex-Split mode. > > This patch adds support to firstl

Re: [PATCH] x86: entry: flush the cache if syscall error

On Thu, 11 Oct 2018, Kristen C Accardi wrote: > On Thu, 2018-10-11 at 13:55 -0700, Kees Cook wrote: > > I think this looks like a good idea. It might be worth adding a > > comment about the checks to explain why those errors are whitelisted. > > It's a cheap and effective mitigation for "unknown fu

[PATCH v2 1/7] modules: Create rlimit for module space

This introduces a new rlimit, RLIMIT_MODSPACE, which limits the amount of module space a user can use. The intention is to be able to limit module space allocations that may come from un-privlidged users inserting e/BPF filters. There is unfortunately no cross platform place to perform this accoun

[PATCH v2 3/7] arm/modules: Add rlimit checking for arm modules

This adds in the rlimit checking for the arm module allocator. This has not been tested. Signed-off-by: Rick Edgecombe --- arch/arm/kernel/module.c | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/arch/arm/kernel/module.c b/arch/arm/kernel/module.c index 3ff571c

[PATCH v2 4/7] arm64/modules: Add rlimit checking for arm64 modules

This adds in the rlimit checking for the arm64 module allocator. This has not been tested. Signed-off-by: Rick Edgecombe --- arch/arm64/kernel/module.c | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm64/kernel/module.c b/arch/arm64/kernel/module.c index f0f27aeefb73..ea9794f2f5

[PATCH v2 2/7] x86/modules: Add rlimit checking for x86 modules

This adds in the rlimit checking for the x86 module allocator. Signed-off-by: Rick Edgecombe --- arch/x86/include/asm/pgtable_32_types.h | 3 +++ arch/x86/include/asm/pgtable_64_types.h | 2 ++ arch/x86/kernel/module.c| 7 ++- 3 files changed, 11 insertions(+), 1 deletion(-)

[PATCH v2 6/7] sparc/modules: Add rlimit for sparc modules

This adds in the rlimit checking for the sparc module allocator. This has not been tested. Signed-off-by: Rick Edgecombe --- arch/sparc/kernel/module.c | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/sparc/kernel/module.c b/arch/sparc/kernel/module.c index df39580f398d..24854fdfa7

[PATCH v2 7/7] s390/modules: Add rlimit checking for s390 modules

This adds in the rlimit checking for the s390 module allocator. This has not been tested. Signed-off-by: Rick Edgecombe --- arch/s390/kernel/module.c | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/arch/s390/kernel/module.c b/arch/s390/kernel/module.c index d298

[PATCH v2 5/7] mips/modules: Add rlimit checking for mips modules

This adds in the rlimit checking for the mips module allocator. This has not been tested. Signed-off-by: Rick Edgecombe --- arch/mips/kernel/module.c | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/arch/mips/kernel/module.c b/arch/mips/kernel/module.c index 49160

[PATCH v2 0/7] Rlimit for module space

Hi, This is v2 of a patch series that was first sent to secur...@kernel.org. The recommendation was to pursue the fix on public lists. First I’ll describe the issue that this is trying to solve, and then the general solution being proposed, and lastly summarize the feedback so far. At a high level

Re: [PATCH] x86/tsc: use real seqcount_latch in cyc2ns_read_begin()

Hi Eric, I love your patch! Perhaps something to improve: [auto build test WARNING on tip/x86/core] [also build test WARNING on v4.19-rc7 next-20181011] [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

Re: [PATCHv2] mm/gup: Cache dev_pagemap while pinning pages

On Thu, Oct 11, 2018 at 11:00 AM Keith Busch wrote: > > Getting pages from ZONE_DEVICE memory needs to check the backing device's > live-ness, which is tracked in the device's dev_pagemap metadata. This > metadata is stored in a radix tree and looking it up adds measurable > software overhead. > >

Re: [PATCH] x86/mm: Do not warn about PCI BIOS W+X mappings

Dear Thomas, Am 08.10.2018 um 21:53 schrieb Thomas Gleixner: PCI BIOS requires the BIOS area 0x0A-0x0FF to be mapped W+X for various legacy reasons. When CONFIG_DEBUG_WX is enabled, this triggers the WX warning, but this is misleading because the mapping is required and is not a result

Re: [mm PATCH v2 4/6] mm: Do not set reserved flag for hotplug memory

On 10/11/2018 3:58 PM, Dan Williams wrote: On Thu, Oct 11, 2018 at 3:18 PM Alexander Duyck wrote: The general suspicion at this point is that the setting of the reserved bit is not really needed for hotplug memory. In addition the setting of this bit results in issues for DAX in that it is not

Re: [PATCH] x86: entry: flush the cache if syscall error

On Thu, 11 Oct 2018, Jann Horn wrote: > On Thu, Oct 11, 2018 at 10:56 PM Kees Cook wrote: > > Seems like just changing this with "ax == 0" into "ax >= 0" would solve > > that? > > As spender points out on twitter > (https://twitter.com/grsecurity/status/1050497259937370118 - thanks, > spender!),

Re: [mm PATCH v2 4/6] mm: Do not set reserved flag for hotplug memory

On Thu, Oct 11, 2018 at 3:18 PM Alexander Duyck wrote: > > The general suspicion at this point is that the setting of the reserved bit > is not really needed for hotplug memory. In addition the setting of this > bit results in issues for DAX in that it is not possible to assign the > region to KVM

[PATCH] random: Move rand_initialize() earlier

Right now rand_initialize() is run as an early_initcall(), but it only depends on timekeeping_init() (for mixing ktime_get_real() into the pools). However, the call to boot_init_stack_canary() for stack canary initialization runs earlier, which triggers a warning at boot: random: get_random_bytes

  1   2   3   4   5   6   7   8   9   10   >