From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: [patch 02/22] x86/cpu: Add conistent CPU match macros Date: Fri, 20 Mar 2020 21:27:58 +0100 Message-ID: <87h7yipy9d.fsf@nanos.tec.linutronix.de> References: <20200320131345.635023594@linutronix.de> <20200320131508.826011988@linutronix.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org To: Andy Shevchenko Cc: LKML , "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" , Greg Kroah-Hartman , Mark Gross , Tony Luck , Paolo Bonzini , Darren Hart , Andy Shevchenko , "Rafael J. Wysocki" , Len Brown , ACPI Devel Maling List , Viresh Kumar , Linux PM , Srinivas Pandruvada , linux-edac@vger.kernel.org, Platform Driver , Jean Delvare , Guenter Roeck li List-Id: platform-driver-x86.vger.kernel.org Andy Shevchenko writes: > >> Also a add a few model constants for Centaur CPUs and QUARK. > > I would perhaps made this as a separate change(s). Can do. >> +#define X86_MATCH_VENDOR_FAM_MODEL_FEATURE(_vendor, _family, _model, \ >> + _feature, _data) { \ > > I would leave it on one line despite the length, but it's up to you. > >> + .vendor = X86_VENDOR_##_vendor, \ >> + .family = _family, \ >> + .model = _model, \ >> + .feature = _feature, \ > >> + .driver_data = (unsigned long) _data \ > > For sake of consistency shouldn't be this kernel_ulong_t ? I can change that though in kernel space this does not matter. > Or we are going to get rid of that type? No. Thanks, tglx