[PATCH 14/17] Update the rsxx flash adapter driver to use ida helper functions.

Signed-off-by: Lee Duncan --- drivers/block/rsxx/core.c | 16 ++-- 1 file changed, 2 insertions(+), 14 deletions(-) diff --git a/drivers/block/rsxx/core.c b/drivers/block/rsxx/core.c index d8b2488aaade..dd23a0e85040 100644 --- a/drivers/block/rsxx/core.c +++ b/drivers/block/rsxx/core

[PATCH 15/17] Update the NVMe SSD driver to use ida helper functions.

Signed-off-by: Lee Duncan --- drivers/block/nvme-core.c | 14 ++ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c index d1d6141920d3..ab13833d4fde 100644 --- a/drivers/block/nvme-core.c +++ b/drivers/block/nvme-core.c

[PATCH 12/17] Update the TI Flash Media driver to use idr helper functions.

Signed-off-by: Lee Duncan --- drivers/misc/tifm_core.c | 17 - 1 file changed, 4 insertions(+), 13 deletions(-) diff --git a/drivers/misc/tifm_core.c b/drivers/misc/tifm_core.c index a511b2a713b3..46385f828a8f 100644 --- a/drivers/misc/tifm_core.c +++ b/drivers/misc/tifm_core.c @

[PATCH 08/17] Update the mmc driver to use idr helper functions.

Signed-off-by: Lee Duncan --- drivers/mmc/core/host.c | 14 -- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/drivers/mmc/core/host.c b/drivers/mmc/core/host.c index 99a9c9011c50..5aa2330f074c 100644 --- a/drivers/mmc/core/host.c +++ b/drivers/mmc/core/host.c @@ -40,9

[PATCH 10/17] Update the DCA DMA driver to use idr helper functions.

Signed-off-by: Lee Duncan --- drivers/dca/dca-sysfs.c | 19 --- 1 file changed, 4 insertions(+), 15 deletions(-) diff --git a/drivers/dca/dca-sysfs.c b/drivers/dca/dca-sysfs.c index 126cf295b198..8930707df295 100644 --- a/drivers/dca/dca-sysfs.c +++ b/drivers/dca/dca-sysfs.c @@ -

Re: [PATCH] ARCNET: fix hard_header_len limit

From: Michael Grzeschik Date: Wed, 16 Sep 2015 14:47:13 +0200 > I have the cleanup patches from Joe Perches and several ARCNET patches > on top, waiting to be posted on the list. What is your Opinion to my > Maintainer Request I send some weeks ago? Please just repost this patch anew, thanks. --

[PATCH 11/17] Update the rtsx multifunction driver to use idr helper functions.

Signed-off-by: Lee Duncan --- drivers/mfd/rtsx_pcr.c | 13 +++-- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/drivers/mfd/rtsx_pcr.c b/drivers/mfd/rtsx_pcr.c index a66540a49079..8ddefb8c5e64 100644 --- a/drivers/mfd/rtsx_pcr.c +++ b/drivers/mfd/rtsx_pcr.c @@ -1191,15 +11

Re: [PATCH V3] mmc: block: Add new ioctl to send multi commands

On Mon, Sep 14, 2015 at 8:00 AM, Jon Hunter wrote: > From: Seshagiri Holi > > Certain eMMC devices allow vendor specific device information to be read > via a sequence of vendor commands. These vendor commands must be issued > in sequence and an atomic fashion. One way to support this would be to

[PATCH 07/17] Update the memstick driver to use idr helper functions.

Signed-off-by: Lee Duncan --- drivers/memstick/core/memstick.c | 19 --- 1 file changed, 4 insertions(+), 15 deletions(-) diff --git a/drivers/memstick/core/memstick.c b/drivers/memstick/core/memstick.c index a0547dbf9806..8f40a3d5108b 100644 --- a/drivers/memstick/core/memstick.

[PATCH 01/17] Add ida and idr helper routines.

Clients of the ida and idr index-management routines tend to use the same calling sequences much of the time, so this change adds helper functions for allocating and releasing indexes of either flavor, i.e. with or without pointer management. Inline functions added for idr: idr_get_index_in_rang

[PATCH 06/17] Update the infiniband uverbs driver to use idr helper functions.

Signed-off-by: Lee Duncan --- drivers/infiniband/core/uverbs_cmd.c | 12 ++-- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/drivers/infiniband/core/uverbs_cmd.c b/drivers/infiniband/core/uverbs_cmd.c index bbb02ffe87df..1e5b2a66a501 100644 --- a/drivers/infiniband/core/u

RE: [PATCH net-next RFC] net: increase LL_MAX_HEADER for Hyper-V

> -Original Message- > From: David Laight [mailto:david.lai...@aculab.com] > Sent: Wednesday, September 16, 2015 9:25 AM > To: Haiyang Zhang ; Vitaly Kuznetsov > ; net...@vger.kernel.org > Cc: David S. Miller ; linux-kernel@vger.kernel.org; > KY Srinivasan ; Jason Wang > Subject: RE: [PA

[PATCH 19/26] [NEWSYSCALL] mm, multi-arch: pass a protection key in to calc_vm_flag_bits()

This plumbs a protection key through calc_vm_flag_bits(). We could of done this in calc_vm_prot_bits(), but I did not feel super strongly which way to go. It was pretty arbitrary which one to use. --- b/arch/powerpc/include/asm/mman.h |5 +++-- b/drivers/char/agp/frontend.c |2 +-

[PATCH 06/26] x86, pkeys: PTE bits for storing protection key

Previous documentation has referred to these 4 bits as "ignored". That means that software could have made use of them. But, as far as I know, the kernel never used them. They are still ignored when protection keys is not enabled, so they could theoretically still get used for software purposes.

Re: [PATCH v2 3/9] sparc/sparc64: allocate sys_membarrier system call number

From: Mathieu Desnoyers Date: Wed, 16 Sep 2015 15:05:54 + (UTC) > - On Sep 7, 2015, at 12:15 PM, Mathieu Desnoyers > mathieu.desnoy...@efficios.com wrote: > >> Signed-off-by: Mathieu Desnoyers >> Acked-by: "David S. Miller" >> CC: Andrew Morton >> CC: linux-...@vger.kernel.org >> CC:

Re: 32-bit bio regression with 4.3 [was: Re: cgroup/loop Bad page state oops in Linux v4.2-rc3-136-g45b4b782e848]

On Tue, Sep 15, 2015 at 8:14 AM, Josh Boyer wrote: > On Sat, Sep 12, 2015 at 9:19 AM, Ming Lei wrote: >> On Fri, 11 Sep 2015 17:43:15 -0400 >> Mike Snitzer wrote: >> >>> Ming, Jens, others: >>> >>> Please see this BZ comment that speaks to a 4.3 regression due to the >>> late bio splitting chang

Re: [f2fs-dev] [PATCH v4] f2fs crypto: allocate buffer for decrypting filename

Thanks Chao, Change log from v3: o enhance the code with proper error handling Change log from v1: o fix wrong pointer assignment Chang log from v2: o add one more missing call path: f2fs_encrypted_follow_link >From efd4c9bb6519e3c10ec5081a2dcdbaca81d2 Mon Sep 17 00:00:00 2001 From:

[PATCH 16/26] x86, pkeys: dump PKRU with other kernel registers

I'm a bit ambivalent about whether this is needed or not. Protection Keys never affect kernel mappings. But, they can affect whether the kernel will fault when it touches a user mapping. But, the kernel doesn't touch user mappings without some careful choreography and these accesses don't gener

Re: [PATCH net-next RFC] net: increase LL_MAX_HEADER for Hyper-V

From: David Laight Date: Wed, 16 Sep 2015 16:25:03 + > Am I right in thinking this is adding an extra 96 unused bytes to the front > of almost all skb just so that hyper-v can make its link level header > contiguous with whatever follows (IP header ?). > > Doesn't sound ideal. Agreed, this

[PATCH 17/26] x86, pkeys: dump PTE pkey in /proc/pid/smaps

The protection key can now be just as important as read/write permissions on a VMA. We need some debug mechanism to help figure out if it is in play. smaps seems like a logical place to expose it. arch/x86/kernel/setup.c is a bit of a weirdo place to put this code, but it already had seq_file.h

[PATCH 04/26] x86, pku: define new CR4 bit

There is a new bit in CR4 for enabling protection keys. We will actually enable it later in the series. --- b/arch/x86/include/uapi/asm/processor-flags.h |2 ++ 1 file changed, 2 insertions(+) diff -puN arch/x86/include/uapi/asm/processor-flags.h~pkeys-02-cr4 arch/x86/include/uapi/asm/pr

[PATCH 15/26] x86, pkeys: optimize fault handling in access_error()

We might not strictly have to make modifictions to access_error() to check the VMA here. If we do not, we will do this: 1. app sets VMA pkey to K 2. app touches a !present page 3. do_page_fault(), allocates and maps page, sets pte.pkey=K 4. return to userspace 5. touch instruction reexecutes, but

[PATCH 21/26] [NEWSYSCALL] x86: wire up mprotect_key() system call

This is all that we need to get the new system call itself working on x86. --- b/arch/x86/entry/syscalls/syscall_32.tbl |1 + b/arch/x86/entry/syscalls/syscall_64.tbl |1 + b/arch/x86/include/uapi/asm/mman.h |7 +++ b/mm/Kconfig |1 + 4 file

[PATCH 20/26] [NEWSYSCALL] mm: implement new mprotect_pkey() system call

mprotect_pkey() is just like mprotect, except it also takes a protection key as an argument. On systems that do not support protection keys, it still works, but requires that key=0. Otherwise it does exactly what mprotect does. I expect it to get used like this, if you want to guarantee that any

[PATCH 24/26] [HIJACKPROT] x86, pkeys: mask off pkeys bits in mprotect()

This is a quick hack that puts very x86-specific bits in to mprotect.c. I will fix this up properly if we decide to go forward with the PROT_* scheme for the user ABI for setting up protection keys. --- b/arch/x86/include/uapi/asm/mman.h |9 + b/mm/mprotect.c|

Re: [PATCH 2/7] f2fs: do in batches truncation in truncate_hole

Hi Chao, How about changing the original patch slightly like below? o don't have to use index variable o should not skip the entire dnode indices, when one of them is -ENOENT --- fs/f2fs/file.c | 13 ++--- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/fs/f2fs/file.c b/

[PATCH 04/17] Update the ch driver to use idr helper functions.

Note: when allocating an index, in the error case, where the just-allocated index has to be released, the required locking around the index removal was not present, so this conversion has the side effect of adding locking for that error condition. This should close a possible race condition that co

[PATCH 02/17] Update scsi hosts to use idr for host number mgmt

Each Scsi_Host instance gets a host number starting at 0, but this was implemented with an atomic integer, and rollover wasn't considered. Another problem with this design is that scsi host numbers used by iscsi are never reused, thereby making rollover more likely. This patch converts Scsi_Host in

[PATCH 18/26] x86, pkeys: add Kconfig prompt to existing config option

I don't have a strong opinion on whether we need this or not. Protection Keys has relatively little code associated with it, and it is not a heavyweight feature to keep enabled. However, I can imagine that folks would still appreciate being able to disable it. Here's the option if folks want it.

[PATCH 10/26] x86, pkeys: notify userspace about protection key faults

A protection key fault is very similar to any other access error. There must be a VMA, etc... We even want to take the same action (SIGSEGV) that we do with a normal access fault. However, we do need to let userspace know that something is different. We do this the same way what we did with SE

[PATCH 14/26] x86, pkeys: check VMAs and PTEs for protection keys

Today, for normal faults and page table walks, we check the VMA and/or PTE to ensure that it is compatible with the action. For instance, if we get a write fault on a non-writeable VMA, we SIGSEGV. We try to do the same thing for protection keys. Basically, we try to make sure that if a user do

[PATCH 05/26] x86, pkey: add PKRU xsave fields and data structure(s)

The protection keys register (PKRU) is saved and restored using xsave. Define the data structure that we will use to access it inside the xsave buffer. Note that we also have to widen the printk of the xsave feature masks since this is feature 0x200 and we only did two characters before. ---

[PATCH 08/26] x86, pkeys: store protection in high VMA flags

vma->vm_flags is an 'unsigned long', so has space for 32 flags on 32-bit architectures. The high 32 bits are unused on 64-bit platforms. We've steered away from using the unused high VMA bits for things because we would have difficulty supporting it on 32-bit. Protection Keys are not available

[PATCH 09/26] x86, pkeys: arch-specific protection bits

Lots of things seem to do: vma->vm_page_prot = vm_get_page_prot(flags); and the ptes get created right from things we pull out of ->vm_page_prot. So it is very convenient if we can store the protection key in flags and vm_page_prot, just like the existing permission bits (_PAGE_RW/PRESE

[PATCH 00/26] [RFCv2] x86: Memory Protection Keys

MM reviewers, if you are going to look at one thing, please look at patch 14 which adds a bunch of additional vma/pte permission checks. Everybody else, please take a look at the two syscall alternatives, especially the non-x86 folk. This is a second big, fat RFC. This code is not runnable to an

[PATCH 13/26] mm: simplify get_user_pages() PTE bit handling

The current get_user_pages() code is a wee bit more complicated than it needs to be for pte bit checking. Currently, it establishes a mask of required pte _PAGE_* bits and ensures that the pte it goes after has all those bits. We need to use the bits for our _PAGE_PRESENT check since pte_present

[PATCH 11/26] x86, pkeys: add functions for set/fetch PKRU

This adds the raw instructions to access PKRU as well as some accessor functions that correctly handle when the CPU does not support the instruction. We don't use them here, but we will use read_pkru() in the next patch. I do not see an immediate use for write_pkru(). But, we put it here for pa

Re: [PATCH v2 3/9] sparc/sparc64: allocate sys_membarrier system call number

- On Sep 16, 2015, at 1:57 PM, David Miller da...@davemloft.net wrote: > From: Mathieu Desnoyers > Date: Wed, 16 Sep 2015 15:05:54 + (UTC) > >> - On Sep 7, 2015, at 12:15 PM, Mathieu Desnoyers >> mathieu.desnoy...@efficios.com wrote: >> >>> Signed-off-by: Mathieu Desnoyers >>> Acke

Re: [rtc-linux] [PATCH] Fixed ds1390_get_reg returned value

Hi, Your patch is not properly fomatted, it as probably been mangled by your mailer can you resend it properly? Thanks, On 16/09/2015 at 17:51:17 +0200, Ivan Grimaldi wrote : > spi_write_then_read puts in rx_buf the received data starting from the > first byte of the rx_buf for n_rx bytes. > >

Re: [PATCH 5/7] f2fs: enhance multithread dio write performance

Hi Chao, On Wed, Sep 16, 2015 at 06:15:55PM +0800, Chao Yu wrote: > Hi Jaegeuk, > > > -Original Message- > > From: Jaegeuk Kim [mailto:jaeg...@kernel.org] > > Sent: Wednesday, September 16, 2015 5:21 AM > > To: Chao Yu > > Cc: linux-f2fs-de...@lists.sourceforge.net; linux-kernel@vger.kern

Re: [PATCH 0/3] VME bus error handling overhaul

> On 16 Sep 2015, at 11:55, Dmitry Kalinkin wrote: > > >> On 16 Sep 2015, at 11:53, Greg Kroah-Hartman >> wrote: >> >> On Wed, Sep 16, 2015 at 11:39:22AM -0400, Dmitry Kalinkin wrote: >>> On 05 Aug 2015, at 16:12, Greg Kroah-Hartman wrote: On Mon, Jul 06, 2015 at 01:3

[PATCH 3/4] drm: Move exynos "match_add all devices matching my drivers" to core.

This is a really nice way to handle the component setup. The subsystem driver knows that it's got a bunch of component drivers, and for any devices that matched its component drivers, it wants all of those to bind to it as master. Signed-off-by: Eric Anholt --- drivers/gpu/drm/drm_platform_help

drm: Platform helpers for exynos-style component registration.

I had previously modeled vc4 off of msm's component driver registration, but on further investigation exynos has an even cleaner way of doing it. Here's a series to turn exynos's style into core helpers, and use it from msm. The patches are build tested, but I don't have either of the platforms t

[PATCH 4/4] drm/msm: Use exynos's model for handling component driver matching.

This eliminates the need for the "connectors" and "gpus" nodes in the devicetree, which we were doing nothing connector- or gpu-specific with. Signed-off-by: Eric Anholt --- drivers/gpu/drm/msm/msm_drv.c | 65 +-- include/drm/drmP.h| 2 +- 2 f

[PATCH 2/4] drm/msm: Use drm_platform_register/unregister_drivers().

This matches how exynos handles the registration of its component drivers. Signed-off-by: Eric Anholt --- drivers/gpu/drm/msm/adreno/adreno_device.c | 12 +--- drivers/gpu/drm/msm/dsi/dsi.c | 16 +--- drivers/gpu/drm/msm/dsi/dsi.h | 2 -- drivers/gp

[PATCH 1/4] drm: Put platform driver registration/unregistration loops in core.

This is mostly just a move of the code from exynos, with a slight reformat. I wanted to do a similar thing for vc4, and msm looks like a good candidate as well. Signed-off-by: Eric Anholt --- drivers/gpu/drm/Makefile| 3 ++- drivers/gpu/drm/drm_platform_helpers.c | 45

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

Sorry for the delay. It is starred in my inbox and I plan to resend the patches. Just did not have time yet. On Wed, Sep 16, 2015 at 3:38 AM, Peter Hurley wrote: > On Tue, Sep 8, 2015 at 8:48 AM, Dmitry Vyukov wrote: >> tty_buffer_flush frees not acquired buffers. >> As the result, for example,

[PATCH v5] x86/asm/entry/32, selftests: Add 'test_syscall_vdso' test

This new test checks that all x86 registers are preserved across 32-bit syscalls. It tests syscalls through VDSO (if available) and through INT 0x80, normally and under ptrace. If kernel is a 64-bit one, high registers (r8..r15) are poisoned before the syscall is called and are checked afterwards.

Re: [RFC PATCH v2 6/9] arm: allocate sys_membarrier system call number

- On Sep 7, 2015, at 12:15 PM, Mathieu Desnoyers mathieu.desnoy...@efficios.com wrote: > [ Untested on this architecture. To try it out: fetch linux-next/akpm, > apply this patch, build/run a membarrier-enabled kernel, and do make > kselftest. ] Hi, We tested the system call on our ARM bo

Re: [PATCH 06/17] Update the infiniband uverbs driver to use idr helper functions.

On 09/16/2015 01:50 PM, Lee Duncan wrote: > Signed-off-by: Lee Duncan Looks OK to me. The setting of uobj->id is no longer under the lock, but we won't succeed at an idr lookup until it is set, which means it won't be found and can't be used in idr_remove_uobj() until after the uobj->id is set r

[PATCH] staging: wilc1000: Added spaces

Added spaces around '=' to remove coding style errors detected by checkpatch.The errors are given below: drivers/staging/wilc1000/host_interface.c:7951: ERROR: spaces required around that '=' (ctx:VxV) drivers/staging/wilc1000/host_interface.c:7952: ERROR: spaces required around that '=' (ctx:VxW)

Re: [PATCH 5/6] pinctrl: mediatek: Remove unneded semicolon

On Wed, 2015-09-16 at 10:28 +0200, Javier Martinez Canillas wrote: > It's not needed an is just creating a null statement, so remove it. > > Signed-off-by: Javier Martinez Canillas > --- > > drivers/pinctrl/mediatek/pinctrl-mtk-common.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) >

Re: [PATCH cgroup/for-4.3-fixes 1/2] Revert "cgroup: simplify threadgroup locking"

Both patches in combination Tested-by: Christian Borntraeger # on top of 4.3-rc1 As a side note, patch 2 does not apply cleanly on 4.2, so we probably need to provide a separate backport. Christian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a mes

Re: [PATCH] irqchip: bcm2835: Add FIQ support

Russell King - ARM Linux writes: > On Wed, Sep 16, 2015 at 10:02:32AM -0400, Eric Anholt wrote: >> Russell King - ARM Linux writes: >> >> > On Mon, Sep 14, 2015 at 07:33:09AM -0700, Eric Anholt wrote: >> >> So, while FIQ isn't used in upstream, I think it's worthwhile to merge. >> >> It is anot

Re: [PATCH 0/2] perf: we can now read separate debug-info files based on a build ID

Hi. This is a gentle ping. This patch fixes a real bug, and it'd be great if it was merged. Here's a demo. This is on a recent Debian/sid box, tracing malloc() calls in emacs. The debug symbols for libc and emacs are split into separate (installed) packages, as is the norm. $ perf probe -x /l

Re: [PATCH v2] coccinelle: tests: unsigned value cannot be lesser than zero

> As we discussed earlier I have dropped idea of adding v <= 0 as it is widely > used in checking ranges, counters, quantities. I find that such a design decision will need more fine-tuning of the suggested small SmPL script. > +@r depends on context || org || report@ > +position p; > +typedef u

Re: [PATCH v2] ata: pata_macio: Fix module autoload for OF platform driver

On Wed, Sep 16, 2015 at 01:48:23PM -0400, Tejun Heo wrote: > On Tue, Sep 15, 2015 at 06:31:14PM +0200, Luis de Bethencourt wrote: > > This platform driver has a OF device ID table but the OF module > > alias information is not created so module autoloading won't work. > > > > This patch adds the m

[PATCH 0/7] arm64: Use contigous PTE bit for the kernel linear mapping

When running 64k pages it became apparent that it was possible that the kernel could create more TLB pressure in certain circumstances when compared to the 4k page kernel. This is due to the fact that large portions of the 4k kernel can be mapped with 2M blocks. While the larger block size for 64k

[PATCH 3/7] arm64: PTE/PMD contiguous bit definition

Define the bit positions in the PTE and PMD for the contiguous bit. Signed-off-by: Jeremy Linton --- arch/arm64/include/asm/pgtable-hwdef.h | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/arm64/include/asm/pgtable-hwdef.h b/arch/arm64/include/asm/pgtable-hwdef.h index 4489cf6.

[PATCH 6/7] arm64: Make the kernel page dump utility aware of the CONT bit

The kernel page dump utility needs to be aware of the CONT bit before it will break up pages ranges for display. Signed-off-by: Jeremy Linton --- arch/arm64/mm/dump.c | 18 +- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/arch/arm64/mm/dump.c b/arch/arm64/mm/dump.

[PATCH 7/7] arm64: Mark kernel page ranges contiguous

With 64k pages, the next larger segment size is 512M. The linux kernel also uses different protection flags to cover its code and data. Because of this requirement, the vast majority of the kernel code and data structures end up being mapped with 64k pages instead of the larger pages common with a

[PATCH 1/7] arm64: Add contiguous page flag shifts and constants

Add the number of pages required to form a contiguous range, as well as some supporting constants. Signed-off-by: Jeremy Linton --- arch/arm64/include/asm/page.h | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/arch/arm64/include/asm/page.h b/arch/arm64/include/asm/page

[PATCH 4/7] arm64: Macros to check/set/unset the contiguous bit

Add the supporting macros to check if the contiguous bit is set, set the bit, or clear it in a PTE entry. Signed-off-by: Jeremy Linton --- arch/arm64/include/asm/pgtable.h | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/arm64/include/asm/pgtable.h b/arch/arm64/include/asm/p

[PATCH 5/7] arm64: Default kernel pages should be contiguous

The default page attributes for a PMD being broken should have the CONT bit set. Create a new definition for an early boot range of PTE's that are contiguous. Signed-off-by: Jeremy Linton --- arch/arm64/include/asm/pgtable.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/includ

[PATCH 2/7] arm64: Shorten lines which exceed 80 characters

PTE definitions in this file exceed 80 characters Signed-off-by: Jeremy Linton --- arch/arm64/include/asm/pgtable-hwdef.h | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/arch/arm64/include/asm/pgtable-hwdef.h b/arch/arm64/include/asm/pgtable-hwdef.h index 24

Pcie bus enumeration and 64bit issues

Hello all, For a big system i use an external pcie enclosure. Unfortunately the bios fails to properly initialise the system. As work around i plan to start the chassis after the linux kernel has booted. This leads to some other problems i would like to discuss here/get pointers to kernel code

Re: [PATCH v2 0/2] of: Dynamic DT updates

Hi Rob, > On Sep 16, 2015, at 19:43 , Rob Herring wrote: > > On Wed, Sep 16, 2015 at 11:11 AM, Pantelis Antoniou > wrote: >> The two patches add a new API for using changeset which >> makes things considerably easier. >> >> This patchset applies against Linus's tree as of today and >> is depen

Re: [PATCH v5 3/4] of: overlay: add per overlay sysfs attributes

Hi Rob, > On Sep 16, 2015, at 19:45 , Rob Herring wrote: > > On Wed, Sep 16, 2015 at 11:09 AM, Pantelis Antoniou > wrote: >> The two default overlay attributes are: >> >> * A targets sysfs attribute listing the targets of the installed >> overlay. The targets list the path on the kernel's devi

[PATCH v2] regulator: core: Make error messages more informative

The same error print exists 4 times in the regulator core : operation not allowed Unfortunately, seeing this in the dmesg is not very informative. Add what type of operation is not allowed to the message so that these errors are unique, hopefully pointing developers in the right direction

Re: [PATCH] irqchip: bcm2835: Add FIQ support

On Wed, Sep 16, 2015 at 05:21:57PM +0100, Russell King - ARM Linux wrote: > On Wed, Sep 16, 2015 at 10:02:32AM -0400, Eric Anholt wrote: > > Russell King - ARM Linux writes: > > > > > On Mon, Sep 14, 2015 at 07:33:09AM -0700, Eric Anholt wrote: > > >> So, while FIQ isn't used in upstream, I think

Re: [PATCH v1 1/2] soc: ti: display firmware file name as part of boot log

On 9/16/2015 10:01 AM, Murali Karicheri wrote: On 09/15/2015 05:20 PM, santosh shilimkar wrote: On 9/15/2015 11:14 AM, Murali Karicheri wrote: On 09/09/2015 12:38 PM, Murali Karicheri wrote: [..] Santosh, I have checked v4.3-rc1 and I don't see it. Did you send the pull request? They are

Re: [PATCH 2/2] ASoC: sunxi: add support for the on-chip codec on early Allwinner SoCs

On Sat, Sep 12, 2015 at 03:26:24PM +0200, Maxime Ripard wrote: This looks pretty good, there's a few minor things below but I'll apply anyway - please send followup patches fixing these. > + if (clk_set_rate(scodec->clk_module, clk_freq)) > + return -EINVAL; Better to pass back t

Re: [PATCH 1/4] drm: Put platform driver registration/unregistration loops in core.

On Wed, Sep 16, 2015 at 11:14 AM, Eric Anholt wrote: > This is mostly just a move of the code from exynos, with a slight > reformat. I wanted to do a similar thing for vc4, and msm looks like > a good candidate as well. > > Signed-off-by: Eric Anholt > --- > drivers/gpu/drm/Makefile

[PATCH v2] mmc: pxamci: fix card detect with slot-gpio API

Move pxamci to mmc slot-gpio API to fix interrupt request. It fixes the case where the card detection is on a gpio expander, on I2C for example on zylonite board. In this case, the card detect netsted interrupt is called from a threaded interrupt. The request_irq() fails, because a hard irq cannot

Re: [PATCH] driver core: Ensure proper suspend/resume ordering

On Wed, 16 Sep 2015, Thierry Reding wrote: > > > Perhaps moving to the end of the list needs to be a little smarter. That > > > is it could check whether the device has been prepared for suspension or > > > not and only move when it hasn't? > > > > Maybe. But doesn't that mean it won't solve you

Re: [PATCH v5 10/10] ASoC: rockchip_i2s: modify DMA max burst to 1

On Mon, Sep 14, 2015 at 07:49:42AM +0800, Shawn Lin wrote: > + default: > + dev_info(&pdev->dev, "Default no dma_quirk!\n"); > + break; > + } Probably printing a message when not using the quirk is a bit noisy (hopefully future devices will fix this!). Otherwise

Re: [PATCH v2] ata: pata_macio: Fix module autoload for OF platform driver

On Tue, Sep 15, 2015 at 06:31:14PM +0200, Luis de Bethencourt wrote: > This platform driver has a OF device ID table but the OF module > alias information is not created so module autoloading won't work. > > This patch adds the missing MODULE_DEVICE_TABLE() for OF to export > that information so m

Re: [PATCH 1/3] dmaengine: virt-dma: don't always free descriptor upon completion

Robert Jarzmik writes: > Robert Jarzmik writes: > Hi Jun, Lars-Peter and Vinod, > > The revert of the former patch of this type, 8c8fe97b2b8a ("Revert "dmaengine: > virt-dma: don't always free descriptor upon completion"") broke pxa_dma > driver. So ... what's the plan, Vinod ? I need to fix px

Re: [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

On 09/16/2015 10:27 AM, Al Stone wrote: > On 09/16/2015 10:24 AM, Al Stone wrote: >> On 09/15/2015 08:44 PM, Rafael J. Wysocki wrote: >>> On Tuesday, September 15, 2015 03:13:12 PM Al Stone wrote: On 09/09/2015 03:09 PM, Al Stone wrote: > Currently, the BAD_MADT_ENTRY macro is used to do a

Re: [PATCH] driver core: Ensure proper suspend/resume ordering

On Wed, 16 Sep 2015, Grygorii Strashko wrote: > I think, It should prohibited to probe devices during suspend/hibernation. > And solution introduced in this patch might help to fix it - > in general, we could do : > - add sync point on suspend enter: wait_for_device_probe() and > - prohibit probin

[PATCH v2] atm: deal with setting entry before mkip was called

If we didn't call ATMARP_MKIP before ATMARP_ENCAP the VCC descriptor is non-existant and we'll end up dereferencing a NULL ptr: [1033173.491930] kasan: GPF could be caused by NULL-ptr deref or user memory accessirq event stamp: 123386 [1033173.493678] general protection fault: [#1] PREEMPT S

Re: [PATCH v4 04/52] PCI: Optimize bus min_align/size calculation during sizing

On Tue, Sep 15, 2015 at 7:57 AM, Bjorn Helgaas wrote: > > Any future series you post should be based on the most recent -rc1 at > the time. I apply patches to branches based on -rc1 unless they > actually depend on something merged after -rc1. ok, will post v5 based on v4.3-rc1. Thanks Yinghai

Re: [PATCH v4 04/22] of: add function to allow probing a device from a OF node

On Wed, Sep 16, 2015 at 10:17:43AM +0200, Tomeu Vizoso wrote: > AFAICS, this is a must currently for correct operation in simple-bus > and simple-mfd situations, because probing order is currently very > unpredictable and it's totally possible for the probing of a child to > start before the probi

Re: [PATCH 1/3] regmap: irq: add support for chips who have separate unmask registers

On Mon, Sep 14, 2015 at 09:40:08AM +, Barry Song wrote: > --- a/include/linux/regmap.h > +++ b/include/linux/regmap.h > @@ -800,12 +800,15 @@ struct regmap_irq { > * > * @status_base: Base status register address. > * @mask_base: Base mask register address. > + * @unmask_base: Base un

Re: [PATCH v4] Input: Add userio module

Hi On Thu, Jul 23, 2015 at 7:33 PM, Stephen Chandler Paul wrote: > Debugging input devices, specifically laptop touchpads, can be tricky > without having the physical device handy. Here we try to remedy that > with userio. This module allows an application to connect to a character > device provi

Re: [PATCH 2/3] regmap: irq: add ack_invert flag for chips using cleared bits as ack

On Mon, Sep 14, 2015 at 09:40:09AM +, Barry Song wrote: > From: Guo Zeng > > An user will be CSR SiRFSoC ARM chips. This is fine but appears to depend on the previous patch. signature.asc Description: Digital signature

Re: [PATCH 2/2] ASoC: atmel-classd: DT binding for Class D audio amplifier driver

On Tue, Sep 15, 2015 at 11:11:53AM +0800, Wu, Songjun wrote: > I try to use one entry, but there is a problem. > It's about 'driver_data' in struct device. > In function snd_soc_register_card, the parameter 'card' will be set to > 'driver_data' by the code 'dev_set_drvdata(card->dev, card)'. > The

[PATCH] ARM: pxa: add wm9713 codec

The mioa701 is using the wm9713 for audio, battery and touchscreen. Add the missing audio part, which disappeared. Signed-off-by: Robert Jarzmik --- arch/arm/mach-pxa/mioa701.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/mach-pxa/mioa701.c b/arch/arm/mach-pxa/mioa701.c index a

Re: Pcie bus enumeration and 64bit issues

On Wed, Sep 16, 2015 at 12:08 PM, Ruudgoogle wrote: > > For a big system i use an external pcie enclosure. Unfortunately the bios > fails to properly initialise the system. As work around i plan to start the > chassis after the linux kernel has booted. This leads to some other problems > i wou

[PATCH 2/2] x86/math-emu: Remove define layer for undocumented opcodes

No code changes. Signed-off-by: Denys Vlasenko CC: Ingo Molnar CC: Borislav Petkov CC: "H. Peter Anvin" CC: Andy Lutomirski CC: Kees Cook CC: x...@kernel.org CC: linux-kernel@vger.kernel.org --- arch/x86/math-emu/fpu_entry.c | 29 + 1 file changed, 9 insertions(+

[PATCH 1/2] x86/math-emu: Add support for FCMOVcc and F[U]COMI[P] insns

Run-tested by booting with "no387 nofxsr" and running test programs: # ./test_FCMOV [RUN] Testing fcmovCC instructions [OK]fcmovCC # ./test_FCOMI [RUN] Testing f[u]comi[p] instructions [OK]f[u]comi[p] Signed-off-by: Denys Vlasenko CC: Ingo Molnar CC: Borislav Petkov CC: "H. Peter A

Re: [PATCH 1/2] x86/math-emu: Add support for FCMOVcc and F[U]COMI[P] insns

On 09/16/2015 09:48 PM, Denys Vlasenko wrote: > Run-tested by booting with "no387 nofxsr" and running test programs: > > # ./test_FCMOV > [RUN] Testing fcmovCC instructions > [OK] fcmovCC > # ./test_FCOMI > [RUN] Testing f[u]comi[p] instructions > [OK] f[u]comi[p] The sources for these test pro

Re: [PATCH v2 4/9] parisc: allocate sys_membarrier system call number

On 16.09.2015 17:07, Mathieu Desnoyers wrote: > - On Sep 7, 2015, at 12:15 PM, Mathieu Desnoyers > mathieu.desnoy...@efficios.com wrote: > >> Signed-off-by: Mathieu Desnoyers >> Tested-by: Helge Deller >> CC: Andrew Morton >> CC: linux-...@vger.kernel.org >> CC: "James E.J. Bottomley" >>

Re: [PATCH 3/3] tps65912: Cleanup TPS65912 subdevice configuration dependencies

On Tue, Sep 15, 2015 at 12:57:41PM -0500, Andrew F. Davis wrote: > The TPS65912 subdevices depend on the mfd core and not any particular > interface. The core is only enabled by enabling an interface so this > is safe. Acked-by: Mark Brown signature.asc Description: Digital signature

[PATCH] pidns: fix set/getpriority and ioprio_set/get in PRIO_USER mode

setpriority(PRIO_USER, 0, x) will change the priority of tasks outside of the current pid namespace. This is in contrast to both the other modes of setpriority and the example of kill(-1). Fix this. getpriority and ioprio have the same failure mode, fix them too. Signed-off-by: Ben Segall Cc: Ole

Re: [PATCH] fs-writeback: drop wb->list_lock during blk_finish_plug()

On Wed 16-09-15 11:16:21, Chris Mason wrote: > On Mon, Sep 14, 2015 at 01:06:25PM -0700, Linus Torvalds wrote: > > On Sun, Sep 13, 2015 at 4:12 PM, Dave Chinner wrote: > > > > > > Really need to run these numbers on slower disks where block layer > > > merging makes a difference to performance. >

Re: [PATCH] fs-writeback: drop wb->list_lock during blk_finish_plug()

On Wed, Sep 16, 2015 at 09:58:06PM +0200, Jan Kara wrote: > On Wed 16-09-15 11:16:21, Chris Mason wrote: > > Short version, Linus' patch still gives bigger IOs and similar perf to > > Dave's original. I should have done the blktrace runs for 60 seconds > > instead of 30, I suspect that would even

Re: First kernel patch (optimization)

On Wed, Sep 16, 2015 at 05:03:39PM +0100, Eric Curtin wrote: > Hi Greg, > > As I said in the subject of the mail (which I have been since told I > shouldn't have done this), I'm a noob to kernel code. I tried to pick > off something super simple to just see what the process of getting a > patch in

[PATCH v3 4/7] fs: Limit file caps to the user namespace of the super block

Capability sets attached to files must be ignored except in the user namespaces where the mounter is privileged, i.e. s_user_ns and its descendants. Otherwise a vector exists for gaining privileges in namespaces where a user is not already privileged. Add a new helper function, in_user_ns(), to te

[PATCH v3 0/7] Initial support for user namespace owned mounts

This is the third revision of the patch series to introduce the concept of superblocks owned by user namespaces. These are nearly identical to the v2 patches; the only changes are resolving conflicts from rebasing onto 4.3-rc1 and reverting a change I inadvertantly introduced in v2. These are the

<    2   3   4   5   6   7   8   9   10   >