Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755410AbbGTPy0 (ORCPT ); Mon, 20 Jul 2015 11:54:26 -0400 Received: from mail-wi0-f173.google.com ([209.85.212.173]:33340 "EHLO mail-wi0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755040AbbGTPyZ (ORCPT ); Mon, 20 Jul 2015 11:54:25 -0400 MIME-Version: 1.0 In-Reply-To: <20150720074040.GB10802@gmail.com> References: <1437326516-13689-1-git-send-email-minipli@googlemail.com> <20150720074040.GB10802@gmail.com> Date: Mon, 20 Jul 2015 17:54:23 +0200 Message-ID: Subject: Re: [PATCH 0/2] x86, microcode: __ref / __refdata cleanups From: Mathias Krause To: Ingo Molnar Cc: Borislav Petkov , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , "linux-kernel@vger.kernel.org" , x86-ml Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 933 Lines: 24 On 20 July 2015 at 09:40, Ingo Molnar wrote: > * Mathias Krause wrote: >> arch/x86/kernel/cpu/microcode/core.c | 2 +- >> arch/x86/kernel/cpu/microcode/intel_early.c | 2 +- >> 2 files changed, 2 insertions(+), 2 deletions(-) > > Please merge this into the single x86 patch of the previous series that gets rid > of __ref/__refdata. There's no need to create unnecessary churn. Will do. Just thought it may make sense to split the series due to different maintainers (x86 vs. microcode). What's your opinion on [1], btw? Should patch 2 go through the tip tree as well? [1] https://lkml.org/lkml/2015/7/19/214 Thanks, Mathias -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/