Re: [PATCH 3/3] mm, oom_reaper: clear TIF_MEMDIE for all tasks queued for oom_reaper

Michal Hocko wrote: > The first obvious one is when the oom victim clears its mm and gets > stuck later on. oom_reaper would back of on find_lock_task_mm returning > NULL. We can safely try to clear TIF_MEMDIE in this case because such a > task would be ignored by the oom killer anyway. The flag

Re: [PATCH 1/4] mailbox/omap: store mailbox interrupt type in omap_mbox_device

On 04/07/2016 03:24 PM, Suman Anna wrote: Hi Grygorii, On 04/07/2016 05:32 AM, Grygorii Strashko wrote: On 04/07/2016 02:37 AM, Suman Anna wrote: The interrupt type used for identifying the layout of the interrupt configuration registers between OMAP4+ SoCs and older SoCs is stored only in

Re: [PATCH RFC] sched/fair: let cpu's cfs_rq to reflect task migration

Hi Dietmar, On 6 April 2016 at 20:53, Dietmar Eggemann wrote: > On 06/04/16 09:37, Morten Rasmussen wrote: >> On Tue, Apr 05, 2016 at 06:00:40PM +0100, Dietmar Eggemann wrote: >>> @@ -2893,8 +2906,12 @@ static void attach_entity_load_avg(struct cfs_rq >>> *cfs_rq,

Re: [PATCH v5 04/10] serial: mps2-uart: add MPS2 UART driver

On 01/04/16 15:02, Vladimir Murzin wrote: > This driver adds support to the UART controller found on ARM MPS2 > platform. > > Signed-off-by: Vladimir Murzin > --- > drivers/tty/serial/Kconfig | 12 + > drivers/tty/serial/Makefile |1 + >

Re: [RESEND v2] phy: hi6220: Add missing MFD_SYSCON dependency on HAS_IOMEM

On Wednesday 30 March 2016 01:54 PM, Krzysztof Kozlowski wrote: > On 30.03.2016 17:10, Lee Jones wrote: >> On Wed, 30 Mar 2016, Lee Jones wrote: >> >>> On Wed, 30 Mar 2016, Krzysztof Kozlowski wrote: >>> The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet direct

Re: Re: Re: PG_reserved and compound pages

On Wednesday 06 April 2016 17:33:43 Michal Hocko wrote: > On Wed 06-04-16 17:12:43, Frank Mehnert wrote: > > Hi Michal, > > > > On Wednesday 06 April 2016 17:02:06 Michal Hocko wrote: > > > [CCing linux-mm mailing list] > > > > > > On Wed 06-04-16 13:28:37, Frank Mehnert wrote: > > > > Hi, > > >

Re: [PATCH v6 5/5] vfio/type1: return MSI mapping requirements with VFIO_IOMMU_GET_INFO

On 04/07/2016 12:32 AM, Alex Williamson wrote: > On Mon, 4 Apr 2016 08:30:11 + > Eric Auger wrote: > >> This patch allows the user-space to know whether MSI addresses need to >> be mapped in the IOMMU. The user-space uses VFIO_IOMMU_GET_INFO ioctl and >>

Re: [PATCH V1] mfd: da9063: remove unused struct da9063_irq_data and define EVENTS_BUF_LEN

On Tue, 05 Apr 2016, Steve Twiss wrote: > From: Steve Twiss > > The structure da9063_irq_data and define EVENTS_BUF_LEN are not used, so > remove the redundant entries. > > Signed-off-by: Steve Twiss > > --- > This patch applies

Re: [PATCH] net: mark DECnet as broken

On Thu, 7 Apr 2016 09:22:43 +0200 Vegard Nossum wrote: > There are NULL pointer dereference bugs in DECnet which can be triggered > by unprivileged users and have been reported multiple times to LKML, > however nobody seems confident enough in the proposed fixes to

[PATCH 4/5] regulator: as3722: Add bypass support for LDO6

From: Jon Hunter LD06 on the AS3722 power management IC supports a bypass mode. Bypass is enabled for the LDO by writing the value 0x3F to the voltage select field in the control register for the LDO. Note that this is the same register and field that is used to select the

[PATCH 3/5] regulator: helpers: Ensure bypass register field matches ON value

From: Jon Hunter When checking the bypass state for a regulator, we check to see if any bits in the bypass mask are set. For most cases this is fine because there is typically only a single bit used to determine if the regulator is in bypass. However, for some regulators,

[PATCH 2/5] regulator: core: Use parent voltage from the supply when bypassed

From: Mark Brown When a regulator is in bypass mode it is functioning as a switch returning the voltage set in the regulator will not give the voltage being output by the regulator as it's just passing through its supply. This means that when we are getting the voltage from a

[PATCH 5/5] regulator: as3722: Constify regulator ops

From: Thierry Reding A const pointer to regulator ops is stored in regulator descriptors. The operations never need to be modified, so define them as const as a hint to the compiler that they can go into .rodata. Signed-off-by: Thierry Reding ---

[PATCH] FUSE: Improve aio directIO write performance for size extending writes.

While sending the blocking directIO in fuse, the write request is broken into sub-requests, each of default size 128k and all the requests are sent in non-blocking background mode if async_dio mode is supported by libfuse. The process which issue the write wait for the completion of all the

[PATCH] KVM: x86: mask CPUID(0xD,0x1).EAX against host value

This ensures that the guest doesn't see XSAVE extensions (e.g. xgetbv1 or xsavec) that the host lacks. Cc: sta...@vger.kernel.org Signed-off-by: Paolo Bonzini --- arch/x86/kvm/cpuid.c | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/x86/kvm/cpuid.c

[PATCH v11 17/17] Xen: EFI: Parse DT parameters for Xen specific UEFI

From: Shannon Zhao Add a new function to parse DT parameters for Xen specific UEFI just like the way for normal UEFI. Then it could reuse the existing codes. If Xen supports EFI, initialize runtime services. CC: Matt Fleming Signed-off-by:

[PATCH v11 15/17] ARM64: XEN: Add a function to initialize Xen specific UEFI runtime services

From: Shannon Zhao When running on Xen hypervisor, runtime services are supported through hypercall. Add a Xen specific function to initialize runtime services. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini

[PATCH v11 00/17] Add ACPI support for Xen Dom0 on ARM64

From: Shannon Zhao This patch set adds ACPI support for Xen Dom0 on ARM64. The relevant Xen ACPI on ARM64 design document could be found from [1]. This patch set adds a new FDT node "uefi" under /hypervisor to pass UEFI information. Introduce a bus notifier of AMBA and

Re: linux-next: build warning after merge of the tip tree

Hi Ingo, On Thu, 7 Apr 2016 10:48:33 +0200 Ingo Molnar wrote: > > Indeed - and this only triggers on HAVE_GENERIC_RCU_GUP. > > I've amended the commit. Thanks. -- Cheers, Stephen Rothwell

[PATCH 1/2] drivers: net: cpsw: fix port_mask parameters in ale calls

ALE APIs expect to receive port masks as input values for arguments port_mask, untag, reg_mcast, unreg_mcast. But there are few places in code where port masks are passed left-shifted by cpsw_priv->host_port, like below: cpsw_ale_add_vlan(priv->ale, priv->data.default_vlan,

Re: [PATCH] wlcore: spi: add wl18xx support

"Reizer, Eyal" writes: > Ping on this patch > >> -Original Message- >> From: Eyal Reizer [mailto:eyalrei...@gmail.com] >> Sent: Wednesday, March 30, 2016 4:07 PM >> To: kv...@codeaurora.org; linux-wirel...@vger.kernel.org; >> net...@vger.kernel.org;

[PATCH 2/2] drivers: net: cpsw: drop host_port field from struct cpsw_priv

The host_port field is constantly assigned to 0 and this value has never changed (since time when cpsw driver was introduced. More over, if this field will be assigned to non 0 value it will break current driver functionality. Hence, there are no reasons to continue maintaining this host_port

[PATCH] kbuild/mkspec: support 'update-bootloader'-based systems

From: Jiri Kosina When uninstalling kernel RPM, we're unconditionally calling "new-kernel-pkg --remove". This is useless on systems which are based on 'update-bootloader' script instead. Support update-bootloader removal method as well in case the script is present; contrary

Re: [PATCH v1 1/2] dt/bindings/usb: Add bindings for PIC32 MUSB driver.

On 04/07/2016 06:42 PM, Sergei Shtylyov wrote: > On 4/7/2016 4:02 PM, Purna Chandra Mandal wrote: > Document devicetree binding for the USB controller >>> >>> Device tree. >>> >> ack. >> and USB Phy found on Microchip PIC32 class devices. >>> >>> PHY. >>> >> ack. >>

Re: [PATCH] fs: overlayfs: override creds with the ones from the superblock mounter (fwd)

erride creds with the ones from the superblock mounter Hi Antonio, [auto build test WARNING on v4.6-rc2] [also build test WARNING on next-20160407] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/com

Re: [PATCH v6 2/5] vfio: allow the user to register reserved iova range for MSI mapping

Hi Alex, On 04/07/2016 12:07 AM, Alex Williamson wrote: > On Mon, 4 Apr 2016 08:30:08 + > Eric Auger wrote: > >> The user is allowed to [un]register a reserved IOVA range by using the >> DMA MAP API and setting the new flag: VFIO_DMA_MAP_FLAG_MSI_RESERVED_IOVA. >> It

[GIT PULL] Ceph fix for -rc3

Hi Linus, Please pull the following Ceph RBD patch from git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus This just fixes a few remaining memory allocations in RBD to use GFP_NOIO instead of GFP_ATOMIC. Thanks! sage

Re: [PATCH 1/2] arm64: mem-model: add flatmem model for arm64

On Tue, Apr 05, 2016 at 04:22:51PM +0800, Chen Feng wrote: > We can reduce the memory allocated at mem-map > by flatmem. > > currently, the default memory-model in arm64 is > sparse memory. The mem-map array is not freed in > this scene. If the physical address is too long, > it will reserved too

Re: [PATCH] wlcore: spi: add wl18xx support

"Reizer, Eyal" writes: >> > static const struct of_device_id wlcore_spi_of_match_table[] = { >> > - { .compatible = "ti,wl1271" }, >> > + { .compatible = "ti,wl1271", .data = _data}, >> > + { .compatible = "ti,wl1273", .data = _data}, >> > + { .compatible = "ti,wl1281", .data

Re: [PATCH] sdhci: wakeup from runtime PM

On Thu, Apr 07, 2016 at 11:11:08AM +0200, Ulf Hansson wrote: > On 5 April 2016 at 14:40, Adrian Hunter wrote: > > On 25/03/16 18:05, Ludovic Desroches wrote: > >> Hi, > >> > >> When not using the SDHCI controller, it is logical to save power by > >> suspending > >> it.

[PATCH 05/11] sparc, rwsem: drop superfluous arch specific implementation

From: Michal Hocko sparc basically reuses generic implementation of rwsem so we can reuse the code rather than duplicate it. Signed-off-by: Michal Hocko --- arch/sparc/include/asm/Kbuild | 1 + arch/sparc/include/asm/rwsem.h | 119

[PATCH 09/11] s390, rwsem: provide __down_write_killable

From: Michal Hocko Introduce ___down_write for the fast path and reuse it for __down_write resp. __down_write_killable each using the respective generic slow path (rwsem_down_write_failed resp. rwsem_down_write_failed_killable). Signed-off-by: Michal Hocko ---

[PATCH 01/11] locking, rwsem: get rid of __down_write_nested

From: Michal Hocko This is no longer used anywhere and all callers (__down_write) use 0 as a subclass. Ditch __down_write_nested to make the code easier to follow. This shouldn't introduce any functional change. Acked-by: Davidlohr Bueso Signed-off-by:

Re: Re: Re: PG_reserved and compound pages

On Thu 07-04-16 15:45:02, Frank Mehnert wrote: > On Wednesday 06 April 2016 17:33:43 Michal Hocko wrote: [...] > > Do you map your pages to the userspace? If yes then vma with VM_IO or > > VM_PFNMAP should keep any attempt away from those pages. > > Yes, such memory objects are also mapped to

Re: [RFC v1] mm: SLAB freelist randomization

Thanks for the feedback Kees. I am preparing another RFC version. For the config, I plan on creating an equivalent option for SLUB. Both can benefit from randomizing their freelist order. Thomas On Wed, Apr 6, 2016 at 2:45 PM Kees Cook wrote: > > On Wed, Apr 6, 2016 at

Re: [PATCH v3] drm/gma500: fix double freeing

On Wednesday 09 December 2015 05:50 PM, Patrik Jakobsson wrote: On Wed, Dec 9, 2015 at 12:53 PM, Sudip Mukherjee wrote: On Thu, Oct 08, 2015 at 06:17:48PM +0530, Sudip Mukherjee wrote: We are allocating backing using psbfb_alloc() and so backing->stolen is always

Re: [PATCH] usb: f_mass_storage: test whether thread is running before starting another

Hi, On 7.04.2016 17:25, Alan Stern wrote: On Thu, 7 Apr 2016, Michal Nazarewicz wrote: Sounds good to me. I’d love someone to test this patch (I sadly have no way of doing that at the moment) and with that I can resend it with updated message. Ivaylo should be able to try it. I

[PATCH] block: avoid to call .bi_end_io() recursively

There were reports about heavy stack use by recursive calling .bi_end_io().[1][2][3] Also these patches[1] [2] [3] were posted for addressing the issue. And the idea is basically similar, all serializes the recursive calling of .bi_end_io() by percpu list. This patch still takes the same idea,

[PATCH 02/10] isa: Implement the max_num_isa_dev macro

max_num_isa_dev is a macro to determine the maximum possible number of ISA devices which may be registered in the I/O port address space given the address extent of the ISA devices. The highest base address possible for an ISA device is 0x3FF; this results in 1024 possible base addresses.

Re: Problems with commit a770d946371e ("gpio: pxa: add pin control gpio direction and request")

On 03/27/2016 01:29 PM, Robert Jarzmik wrote: Guenter Roeck writes: Hi, Hi Guenter, when trying pxa_defconfig with various pxa270 and pxa255 qemu targets, I noticed that the gpio pin direction is no longer set. Bisect points to commit a770d946371e ("gpio: pxa: add pin

perf report --no-children chopping off tracepoint fields

Hi Namhyung, If I do: # perf record --call dwarf -p 2519 -e syscalls:sys_enter_open And then run plain 'perf report' I get this on the TUI, perfect: Samples: 1 of event 'syscalls:sys_enter_open', Event count (approx.): 1 Children Self Trace output + 100.00% 100.00%

Re: [LINUX PATCH v2 1/3] spi: Added dummy_cycle entry in the spi_transfer structure.

Hi all, Le 07/04/2016 16:39, P L Sai Krishna a écrit : > This patch adds dummy_cycles entry in the spi_transfer structure. > len field in the transfer structure contains dummy bytes along with > actual data bytes, controllers which requires dummy bytes use len > field and simply Ignore the

Re: [LINUX PATCH v2 2/3] mtd:m25p80: Assigned number of dummy cycles to dummy_cycles.

Hi L, [auto build test ERROR on spi/for-next] [also build test ERROR on v4.6-rc2 next-20160407] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/P-L-Sai-Krishna/spi-Added-dummy_cycle-entry

[PATCH 07/11] alpha, rwsem: provide __down_write_killable

From: Michal Hocko Introduce ___down_write for the fast path and reuse it for __down_write resp. __down_write_killable each using the respective generic slow path (rwsem_down_write_failed resp. rwsem_down_write_failed_killable). Signed-off-by: Michal Hocko ---

[PATCH 0/11] introduce down_write_killable for rw_semaphore v3

Hi, the following patchset implements a killable variant of write lock for rw_semaphore. My usecase is to turn as many mmap_sem write users to use a killable variant which will be helpful for the oom_reaper merged in 4.6-rc1 (aac453635549 ("mm, oom: introduce oom reaper")) to asynchronously tear

[PATCH 10/11] x86, rwsem: provide __down_write_killable

From: Michal Hocko which uses the same fast path as __down_write except it falls back to call_rwsem_down_write_failed_killable slow path and return -EINTR if killed. To prevent from code duplication extract the skeleton of __down_write into a helper macro which just takes the

Re: [PATCH 1/2] x86/arch_prctl: add ARCH_SET_{COMPAT,NATIVE} to change compatible mode

On 04/07/2016 05:39 PM, Andy Lutomirski wrote: On Apr 7, 2016 5:12 AM, "Dmitry Safonov" wrote: On 04/06/2016 09:04 PM, Andy Lutomirski wrote: [cc Dave Hansen for MPX] On Apr 6, 2016 9:30 AM, "Dmitry Safonov" wrote: Now each process that runs

[PATCH 02/11] locking, rwsem: drop explicit memory barriers

From: Michal Hocko sh and xtensa seem to be the only architectures which use explicit memory barriers for rw_semaphore operations even though they are not really needed because there is the full memory barrier is always implied by atomic_{inc,dec,add,sub}_return resp. cmpxchg.

[PATCH 08/11] ia64, rwsem: provide __down_write_killable

From: Michal Hocko Introduce ___down_write for the fast path and reuse it for __down_write resp. __down_write_killable each using the respective generic slow path (rwsem_down_write_failed resp. rwsem_down_write_failed_killable). Signed-off-by: Michal Hocko ---

Re: [RFC PATCH 0/3] restartable sequences v2: fast user-space percpu critical sections

On Thu, Apr 07, 2016 at 05:24:32PM +0200, Peter Zijlstra wrote: > On Thu, Apr 07, 2016 at 07:35:26AM -0700, Andy Lutomirski wrote: > > That way we could take an async signal, handle it, and resume, even in > > the middle of a commit, without aborting. Of course, if the signal > > hander tried to

Re: [RFC PATCH 0/3] restartable sequences v2: fast user-space percpu critical sections

On Thu, Apr 7, 2016 at 8:24 AM, Peter Zijlstra wrote: > On Thu, Apr 07, 2016 at 07:35:26AM -0700, Andy Lutomirski wrote: >> What I meant was: rather than shoving individual values into the TLABI >> thing, shove in a pointer: >> >> struct commit_info { >> u64

Re: Boot failure when using NFS on OMAP based evms

Currently linux-next is failing to boot via NFS on my AM335x GP evm, AM437x GP evm and Beagle X15. I bisected the problem down to the commit "udp: remove headers from UDP packets before queueing". >>> >>> Thanks for the report, and apologies for breaking your configuration. >>> I

Re: [RFC] weird semantics of SG_DXFER_TO_FROM_DEV in BLK_DEV_SKD (drivers/block/skd*)

On Mon, Apr 04, 2016 at 06:16:12PM +0100, Al Viro wrote: > Another fun question: should the normal sg_io() copy the buffer in on > SG_DXFER_TO_FROM_DEV? Right now it doesn't; in !copy case (when it goes > through bio_map_user_iov()) the effect is achieved simply by doing the > read into the pages

Re: [RFC PATCH 0/3] restartable sequences v2: fast user-space percpu critical sections

On Thu, Apr 07, 2016 at 08:44:38AM -0700, Andy Lutomirski wrote: > On Thu, Apr 7, 2016 at 8:24 AM, Peter Zijlstra wrote: > > On Thu, Apr 07, 2016 at 07:35:26AM -0700, Andy Lutomirski wrote: > >> What I meant was: rather than shoving individual values into the TLABI > >>

Re: The most insane proposal in regard to the Linux kernel development

On Thu, Apr 07, 2016 at 02:01:03PM +0500, Artem S. Tashkinov wrote: > On 2016-04-07 01:05, Greg KH wrote: > > On Sat, Apr 02, 2016 at 05:43:47PM +0500, Artem S. Tashkinov wrote: > > > One very big justification of this proposal is that core Linux > > > development > > > (I'm talking about various

Re: [RFC PATCH v1.9 00/14] livepatch: hybrid consistency model

On Thu, Apr 07, 2016 at 02:10:30PM +0200, Petr Mladek wrote: > On Fri 2016-03-25 14:34:47, Josh Poimboeuf wrote: > > TODO: > > - try ftrace handler switching idea from v1 cover letter > > I have had a discussion about it with Mirek. This would help with > kthreads. If they are sleeping in a

[PATCH 06/11] locking, rwsem: introduce basis for down_write_killable

From: Michal Hocko Introduce a generic implementation necessary for down_write_killable. This is a trivial extension of the already existing down_write call which can be interrupted by SIGKILL. This patch doesn't provide down_write_killable yet because arches have to provide

Re: [PATCH] cpu/hotplug: fix rollback during error-out in __cpu_disable()

On 04/06/2016 09:51 PM, Heiko Carstens wrote: > This fixes the issue that a second cpu_down() will take forever, if > __cpu_disable() fails. Yes. But even without the second take down your CPU isn't complete up. > However it does not fix the issue that CPU_DOWN_FAILED will be seen on a >

[PATCH 04/11] sh, rwsem: drop superfluous arch specific implementation

From: Michal Hocko since "locking, rwsem: drop explicit memory barriers" the arch specific code is basically same as the the generic one so we can drop the superfluous code. Suggested-by: Davidlohr Bueso Signed-off-by: Michal Hocko ---

Re: [RFC PATCH v1.9 00/14] livepatch: hybrid consistency model

On Thu, 7 Apr 2016, Josh Poimboeuf wrote: > > > - try ftrace handler switching idea from v1 cover letter [ ... ] > > We probably should not check the stack in atomic context > > Can you elaborate why not? I admittedly forgot what the "ftrace handler switching idea" is, and am not sure where

Re: [PATCH] KVM: x86: mask CPUID(0xD,0x1).EAX against host value

2016-04-07 13:47+0200, Paolo Bonzini: > This ensures that the guest doesn't see XSAVE extensions > (e.g. xgetbv1 or xsavec) that the host lacks. > > Cc: sta...@vger.kernel.org > Signed-off-by: Paolo Bonzini > --- Reviewed-by: Radim Krčmář

[LINUX PATCH v2 2/3] mtd:m25p80: Assigned number of dummy cycles to dummy_cycles.

Assigned number of dummy cycles to dummy_cycles member of spi_transfer structure in m25p80_read API. Signed-off-by: P L Sai Krishna --- v2: - New Patch. drivers/mtd/devices/m25p80.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/mtd/devices/m25p80.c

[LINUX PATCH v2 1/3] spi: Added dummy_cycle entry in the spi_transfer structure.

This patch adds dummy_cycles entry in the spi_transfer structure. len field in the transfer structure contains dummy bytes along with actual data bytes, controllers which requires dummy bytes use len field and simply Ignore the dummy_cycles field. Controllers which expects dummy cycles won't work

Re: [PATCH] devcoredump: add scatterlist support

On Thu, Apr 07, 2016 at 12:47:05PM +0200, Johannes Berg wrote: > Hi Greg, > > On Fri, 2015-12-11 at 11:55 +0100, Johannes Berg wrote: > > From: Aviya Erenfeld > > > > Add scatterlist support (dev_coredumpsg) to allow drivers to avoid > > vmalloc() like dev_coredumpm(),

Re: [PATCH 1/2] x86/arch_prctl: add ARCH_SET_{COMPAT,NATIVE} to change compatible mode

On Apr 7, 2016 5:12 AM, "Dmitry Safonov" wrote: > > On 04/06/2016 09:04 PM, Andy Lutomirski wrote: >> >> [cc Dave Hansen for MPX] >> >> On Apr 6, 2016 9:30 AM, "Dmitry Safonov" wrote: >>> >>> Now each process that runs natively on x86_64 may

Re: Boot failure when using NFS on OMAP based evms

On Thu, Apr 7, 2016 at 10:36 AM, Franklin S Cooper Jr. wrote: > > > On 04/06/2016 09:22 PM, Willem de Bruijn wrote: >> On Wed, Apr 6, 2016 at 7:12 PM, Franklin S Cooper Jr. wrote: >>> Hi All, >>> >>> Currently linux-next is failing to boot via NFS on my AM335x GP

Re: [PATCH v5 04/10] serial: mps2-uart: add MPS2 UART driver

On Thu, Apr 07, 2016 at 02:03:54PM +0100, Vladimir Murzin wrote: > On 01/04/16 15:02, Vladimir Murzin wrote: > > This driver adds support to the UART controller found on ARM MPS2 > > platform. > > > > Signed-off-by: Vladimir Murzin > > --- > > drivers/tty/serial/Kconfig

[PATCH 05/10] iio: stx104: Utilize the module_isa_driver and max_num_isa_dev macros

The Apex Embedded Systems STX104 DAC drivers does not do anything special in module init/exit. This patch eliminates the module init/exit boilerplate code by utilizing the module_isa_driver macro. Additionally, the max_num_isa_dev macro is utilized to simplify the determination of maximum

[PATCH 09/10] gpio: 104-idio-16: Utilize the ISA bus driver

The ACCES 104-IDIO-16 series communicates via the ISA bus. As such, it is more appropriate to use the ISA bus driver over the platform driver to control the ACCES 104-IDIO-16 GPIO driver. This patch also adds support for multiple devices via the base and irq module array parameters. Each element

[PATCH 06/10] watchdog: ebc-c384_wdt: Utilize the ISA bus driver

The WinSystems EBC-C384 watchdog timer is controlled via ISA bus communication. As such, the ISA bus driver is more appropriate than the platform driver for the WinSystems EBC-C384 watchdog timer driver. Signed-off-by: William Breathitt Gray --- drivers/watchdog/Kconfig

[PATCH 07/10] gpio: 104-dio-48e: Utilize the ISA bus driver

The ACCES 104-DIO-48E series communicates via the ISA bus. As such, it is more appropriate to use the ISA bus driver over the platform driver to control the ACCES 104-DIO-48E GPIO driver. This patch also adds support for multiple devices via the base and irq module array parameters. Each element

[LINUX PATCH v2 3/3] spi:zynqmp:gqspi: Added separate dummy entry.

This patch sends dummy as a separate entry. Break the Address+Cmd+dummy transfer into multiple transfers. Address+Cmd as one transfer. Dummy cycles as another transfer. As per the controller spec, immediate data field of dummy entry in the GenFifo represent dummy cycles. Bus width for dummy cycles

[PATCH 01/10] isa: Implement the module_isa_driver macro

The module_isa_driver macro is a helper macro for ISA drivers which do not do anything special in module init/exit. This eliminates a lot of boilerplate code. Each module may only use this macro once, and calling it replaces module_init and module_exit. Signed-off-by: William Breathitt Gray

Re: [PATCH v5 04/10] serial: mps2-uart: add MPS2 UART driver

On 07/04/16 15:43, Greg KH wrote: > No idea, first I've seen of this, and there's no patch here... > Hmm... patch supplied ;) Cheers Vladimir On 01/04/16 15:02, Vladimir Murzin wrote: > This driver adds support to the UART controller found on ARM MPS2 > platform. > > Signed-off-by: Vladimir

[PATCH 00/10] Use the ISA bus driver for PC/104 and ISA devices

This patchset is based on top of commit 3a3a5fece6f2 ("fs: kernfs: Replace CURRENT_TIME by current_fs_time()") of the driver-core-next branch of the driver-core repository. Two new ISA bus driver macros are introduced in this patchset: module_isa_driver and max_num_isa_dev. The module_isa_driver

Re: [RFC PATCH v1.9 07/14] x86/stacktrace: add function for detecting reliable stack traces

On Thu, Apr 07, 2016 at 01:55:52PM +0200, Petr Mladek wrote: > On Fri 2016-03-25 14:34:54, Josh Poimboeuf wrote: > > For live patching and possibly other use cases, a stack trace is only > > useful if you can be assured that it's completely reliable. Add a new > > save_stack_trace_tsk_reliable()

Re: [RFC PATCH v1 1/9] selftest: sync: basic tests for sw_sync framework

On 4 April 2016 at 05:12, Emilio López wrote: > Hi, > > El 28/03/16 a las 10:48, Emil Velikov escribió: > > These tests are based on the libsync test suite from Android. > This commit lays the ground for future tests, as well as includes > tests for a

Re: Oops in 4.6-rc2: NULL pointer dereference in cdc-acm

On Thu, Apr 07, 2016 at 08:59:38AM +0200, Oliver Neukum wrote: > On Wed, 2016-04-06 at 22:48 +0200, Gabriele Mazzotta wrote: > > Hi, > > > > I'm getting a kernel oops when I plug some smartphone via USB to my > > laptop, which is currently running the v4.6-rc2. > > > > The problem seems to be

Re: [RFC PATCH 0/3] restartable sequences v2: fast user-space percpu critical sections

On Thu, Apr 07, 2016 at 07:35:26AM -0700, Andy Lutomirski wrote: > What I meant was: rather than shoving individual values into the TLABI > thing, shove in a pointer: > > struct commit_info { > u64 post_commit_rip; > u32 cpu; > u64 *event; > // whatever else; > }; > > and then put a

[PATCH] usb: wusbcore: remove unreachable code

The call to wusb_dev_sysfs_rm() which is just after return will never be executed. On checking the code, wusb_dev_sysfs_add() is the last one to be executed so even if that fails we do not need wusb_dev_sysfs_rm() in the error path. Signed-off-by: Sudip Mukherjee

Re: [PATCH RFC] select_idle_sibling experiments

On Tue, Apr 05, 2016 at 02:08:22PM -0400, Chris Mason wrote: > Hi everyone, > > We're porting the fb kernel up to 4.5, and one of our last few out-of-tree > patches is a hack to try harder to find idle cpus when waking up tasks. > This helps in pretty much every workload we run, mostly because

[PATCH 03/11] xtensa, rwsem: drop superfluous arch specific implementation

From: Michal Hocko since "locking, rwsem: drop explicit memory barriers" the arch specific code is basically same as the the generic one so we can drop the superfluous code. Suggested-by: Davidlohr Bueso Acked-by: Max Filippov

[PATCH 11/11] locking, rwsem: provide down_write_killable

From: Michal Hocko Now that all the architectures implement the necessary glue code we can introduce down_write_killable. The only difference wrt. regular down_write is that the slow path waits in TASK_KILLABLE state and the interruption by the fatal signal is reported as -EINTR

Re: [RESEND PATCH v7 1/6] mfd: cros_ec: Add MKBP event support

On Tue, 05 Apr 2016, Tomeu Vizoso wrote: > From: Vic Yang > > Newer revisions of the ChromeOS EC add more events besides the keyboard > ones. So handle interrupts in the MFD driver and let consumers register > for notifications for the events they might care. > > To keep

[PATCH] x86: wire up compat readv2/writev2 syscalls

Signed-off-by: Christoph Hellwig Reported-by: David Smith Tested-by: David Smith --- arch/x86/entry/syscalls/syscall_32.tbl | 4 ++-- arch/x86/entry/syscalls/syscall_64.tbl | 2 ++ 2 files changed, 4 insertions(+), 2 deletions(-) diff --git

Re: [PATCH v9 2/4] tpm: Proxy driver for supporting multiple emulated TPMs

On 04/07/2016 08:35 AM, Jarkko Sakkinen wrote: On Tue, Mar 29, 2016 at 02:19:12PM -0400, Stefan Berger wrote: This patch implements a proxy driver for supporting multiple emulated TPMs in a system. The driver implements a device /dev/vtpmx that is used to created a client device pair /dev/tpmX

Re: [PATCH v6 6/7] dma-reserved-iommu: iommu_get/put_single_reserved

Hi Eric, On Thu, Apr 07, 2016 at 11:33:42AM +0200, Eric Auger wrote: > Alex, > On 04/07/2016 01:12 AM, Alex Williamson wrote: > > On Mon, 4 Apr 2016 08:07:01 + > > Eric Auger wrote: > > > >> This patch introduces iommu_get/put_single_reserved. > >> > >>

[PATCH 10/10] gpio: ws16c48: Utilize the ISA bus driver

The WinSystems WS16C48 communicates via the ISA bus. As such, it is more appropriate to use the ISA bus driver over the platform driver to control the WinSystems WS16C48 GPIO driver. This patch also adds support for multiple devices via the base and irq module array parameters. Each element of

[PATCH 08/10] gpio: 104-idi-48: Utilize the ISA bus driver

The ACCES 104-IDI-48 series communicates via the ISA bus. As such, it is more appropriate to use the ISA bus driver over the platform driver to control the ACCES 104-IDI-48 GPIO driver. This patch also adds support for multiple devices via the base and irq module array parameters. Each element of

Re: [PATCH 525/525] Staging: Wilc1000: Fixed coding style ether_addr_copy

On Thu, Apr 07, 2016 at 03:07:15PM +0530, Shyam Saini wrote: > Fixed following warning detected by checkpatch.pl: > warning: Prefer ether_addr_copy() over memcpy() if the Ethernet addressesare > __aligned(2) > > Signed-off-by: Shyam Saini > --- >

[PATCH 03/10] Documentation: Add ISA bus driver documentation

This is a verbatim copy of the original commit message of the initial commit of the ISA bus driver authored by Rene Herman. Descriptions of the module_isa_driver macro and max_num_isa_dev macro are provided at the end. Signed-off-by: William Breathitt Gray ---

[PATCH 04/10] iio: stx104: Change STX104 dependency to ISA_BUS

The Apex Embedded Systems STX104 may be used on 64-bit X86 systems. This patch allows the Apex Embedded Systems STX104 DAC driver to be compiled for both 32-bit and 64-bit X86 systems. Signed-off-by: William Breathitt Gray --- drivers/iio/dac/Kconfig | 2 +- 1 file

Re: [PATCH RFC 1/2] scatterlist: add mempool based chained SG alloc/free api

On 03/15/16 15:39, Ming Lin wrote: +static void sg_mempoll_free(struct scatterlist *sgl, unsigned int nents) Please change mempoll into mempool. Thanks, Bart.

Re: [PATCH] x86/hpet: Reduce HPET counter read contention

On 04/07/2016 12:58 AM, Andy Lutomirski wrote: On Wed, Apr 6, 2016 at 7:02 AM, Waiman Long wrote: On a large system with many CPUs, using HPET as the clock source can have a significant impact on the overall system performance because of the following reasons: 1) There

[PATCH] KVM: new maintainer on the block

Avi has kept Gleb busy enough, and Radim has been helping me for a while, so let's "reward" him with an entry in MAINTAINERS. Acked-by: Gleb Natapov Cc: Radim Krčmář --- Radim, please commit this yourself to kvm/master and kvm/next please!

Re: [PATCH 06/14] coresight: tmc: making prepare/unprepare functions generic

On 22/03/16 20:23, Mathieu Poirier wrote: Dealing with HW related matters in tmc_read_prepare/unprepare becomes convoluted when many cases need to be handled distinctively. As such moving processing related to HW setup to individual driver files and keep the core driver generic. Signed-off-by:

Re: [PATCH 1/3] perf tools: Introduce trim function

On Thursday, April 7, 2016 4:03:21 PM CEST Jiri Olsa wrote: > On Thu, Apr 07, 2016 at 10:50:47AM -0300, Arnaldo Carvalho de Melo wrote: > > Em Thu, Apr 07, 2016 at 09:11:11AM +0200, Jiri Olsa escreveu: > > > To be used in cases for both sides trim. > > > > > > Link: > > >

[PATCH v10 2/4] gadget: Support for the usb charger framework

For supporting the usb charger, it adds the usb_charger_init() and usb_charger_exit() functions for usb charger initialization and exit. It will report to the usb charger when the gadget state is changed, then the usb charger can do the power things. Signed-off-by: Baolin Wang

[PATCH v10 4/4] power: wm831x_power: Support USB charger current limit management

Integrate with the newly added USB charger interface to limit the current we draw from the USB input based on the input device configuration identified by the USB stack, allowing us to charge more quickly from high current inputs without drawing more current than specified from others.

[PATCH v10 3/4] gadget: Integrate with the usb gadget supporting for usb charger

When the usb gadget supporting for usb charger is ready, the usb charger can implement the usb_charger_plug_by_gadget() function and usb_charger_exit() function by getting 'struct usb_charger' from 'struct gadget'. Signed-off-by: Baolin Wang ---

  1   2   3   4   5   6   7   8   9   10   >