[PATCH] macintosh/adb: Use C99 initializers for struct adb_driver instances

Hopefully this will make it easier for the next reader who needs to check these pointers. No change to object files. Cc: Benjamin Herrenschmidt Signed-off-by: Finn Thain --- drivers/macintosh/adb-iop.c| 14 +++---

[PATCH 2/2] misc: ocxl: use put_device() instead of device_unregister()

if device_register() returned an error! Always use put_device() to give up the reference initialized. Signed-off-by: Arvind Yadav --- drivers/misc/ocxl/pci.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/misc/ocxl/pci.c

[PATCH 0/2] misc: use put_device() instead of kfree()

Never directly free @dev after calling device_register(), even if it returned an error! Always use put_device() to give up the reference initialized. Arvind Yadav (2): [PATCH 1/2] misc: mic: Release reference count and memory for VOP device [PATCH 2/2] misc: ocxl: use put_device() instead of

Re: [PATCH] powerpc/mm: Fix section mismatch warning in stop_machine_change_mapping()

Balbir, On 03/11/2018 03:23 AM, Balbir Singh wrote: Looks reasonable, I'd recommend trying to compile with MEMORY_HOTPLUG and MEMORY_HOTREMOVE enabled/disabled as well Thanks for reviewing. I should have mentioned it :) I did that (disable CONFIG_MEMORY_HOTPLUG) and all the related functions

Re: [PATCH v2] On ppc64le we HAVE_RELIABLE_STACKTRACE

On Fri, Mar 09, 2018 at 05:47:18PM +0100, Torsten Duwe wrote: > On Thu, 8 Mar 2018 10:26:16 -0600 > Josh Poimboeuf wrote: > > > This doesn't seem to address some of my previous concerns: > > You're right. That discussion quickly headed towards objtool > and I forgot about

[PATCH v4 00/10] posix_clocks: Prepare syscalls for 64 bit time_t conversion

The series is a preparation series for individual architectures to use 64 bit time_t syscalls in compat and 32 bit emulation modes. This is a follow up to the series Arnd Bergmann posted: https://sourceware.org/ml/libc-alpha/2015-05/msg00070.html [1] Thomas, Arnd, this seems ready to be merged

[PATCH v4 02/10] include: Move compat_timespec/ timeval to compat_time.h

All the current architecture specific defines for these are the same. Refactor these common defines to a common header file. The new common linux/compat_time.h is also useful as it will eventually be used to hold all the defines that are needed for compat time types that support non y2038 safe

Re: [PATCH v3 02/10] include: Move compat_timespec/ timeval to compat_time.h

I posted the updated series. I fixed up the order of include files where I could find some order. There have been other commits that used scripts to do such replacements and have already stomped on the order. For example: commit 7c0f6ba682b9c7632072ffbedf8d328c8f3c42ba Author: Linus Torvalds

Linux 4.16: Reported regressions as of , 2018-03-12 (Was: Linux 4.16-rc5)

On 12.03.2018 01:42, Linus Torvalds wrote: > This continue to be pretty normal - this rc is slightly larger than > rc4 was, but that looks like one of the normal fluctuations Hi! Find below my fourth regression report for Linux 4.16. It lists 9 regressions I'm currently aware of. 1 was fixed

Re: [PATCH] x86, powerpc : pkey-mprotect must allow pkey-0

On 03/09/2018 12:06 PM, Ram Pai wrote: > On Fri, Mar 09, 2018 at 09:19:53PM +1100, Michael Ellerman wrote: >> Ram Pai writes: >> >>> Once an address range is associated with an allocated pkey, it cannot be >>> reverted back to key-0. There is no valid reason for the above

[PATCH 1/2] misc: mic: Release reference count and memory for VOP device

Never directly free @dev after calling device_register(), even if it returned an error! Always use put_device() to give up the reference initialized. Release allocated memory for vop device in vop_release_dev(). Signed-off-by: Arvind Yadav ---

Re: [PATCH v3] powerpc/kernel/sysfs: Export ldbar spr to sysfs

Hi, On Tuesday 06 March 2018 04:35 PM, Michael Ellerman wrote: Anju T Sudhakar writes: diff --git a/arch/powerpc/kernel/sysfs.c b/arch/powerpc/kernel/sysfs.c index 4437c70..caefb64 100644 --- a/arch/powerpc/kernel/sysfs.c +++ b/arch/powerpc/kernel/sysfs.c @@ -757,6

Re: [PATCHv4 1/3] powerpc, cpu: partially unbind the mapping between cpu logical id and its seq in dt

On Mon, 2018-03-12 at 12:43 +0800, Pingfan Liu wrote: > For kexec -p, the boot cpu can be not the cpu0, this causes the problem > to alloc paca[]. In theory, there is no requirement to assign cpu's logical > id as its present seq by device tree. But we have something like >

Re: [PATCHv4 1/3] powerpc, cpu: partially unbind the mapping between cpu logical id and its seq in dt

Hi Pingfan, Thank you for the patch! Yet something to improve: [auto build test ERROR on v4.16-rc4] [also build test ERROR on next-20180309] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH v2 3/4] rfi-flush: Allow pseries to force init of fallback flush area

This ensures the fallback flush area is always allocated at boot time on the pseries platform, so PowerVM migration to an unpatched system can rely on the fallback flush method. Signed-off-by: Mauricio Faria de Oliveira --- arch/powerpc/include/asm/setup.h | 2

Re: [PATCH 2/2] misc: ocxl: use put_device() instead of device_unregister()

On 12/03/18 22:36, Arvind Yadav wrote: if device_register() returned an error! Always use put_device() to give up the reference initialized. Signed-off-by: Arvind Yadav This looks right, thanks for picking it up. Acked-by: Andrew Donnellan

[PATCH v2 1/4] rfi-flush: Move the logic to avoid a redo into the debugfs code

From: Michael Ellerman rfi_flush_enable() includes a check to see if we're already enabled (or disabled), and in that case does nothing. But that means calling setup_rfi_flush() a 2nd time doesn't actually work, which is a bit confusing. Move that check into the debugfs

[PATCH v2 4/4] rfi-flush: Call setup_rfi_flush() after LPM migration

From: Michael Ellerman We might have migrated to a machine that uses a different flush type, or doesn't need flushing at all. Signed-off-by: Michael Ellerman Signed-off-by: Mauricio Faria de Oliveira ---

[PATCH v2 2/4] rfi-flush: Make it possible to call setup_rfi_flush() again

From: Michael Ellerman For PowerVM migration we want to be able to call setup_rfi_flush() again after we've migrated the partition. To support that we need to check that we're not trying to allocate the fallback flush area after memblock has gone away (i.e., boot-time

Re: [PATCH 2/3] rfi-flush: Make it possible to call setup_rfi_flush() again

Hi Michael and Michal, Got back to this; sorry for the delay. On 03/06/2018 09:55 AM, Michal Suchánek wrote: Michael Ellerman wrote: I*think* the patch below is all we need, as well as some tweaking of patch 2, are you able to test and repost? Enabling the fallback

[PATCH v2 0/4] Setup RFI flush after PowerVM LPM migration

This patchset allows for setup_rfi_flush() to be called again after PowerVM LPM (live partition mobility) aka LPAR migration, in order to possibly switch to a different flush method. The patches are mostly from Michael Ellerman, I have rebased to powerpc/linux.git merge branch as of commit