[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1505191515500.4225@nanos>
Date: Tue, 19 May 2015 15:17:57 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Bartosz Golaszewski <bgolaszewski@...libre.com>
cc: LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Viresh Kumar <viresh.kumar@...aro.org>,
Guenter Roeck <linux@...ck-us.net>,
Jean Delvare <jdelvare@...e.de>,
Fenghua Yu <fenghua.yu@...el.com>,
Benoit Cousson <bcousson@...libre.com>,
Jonathan Corbet <corbet@....net>,
Oleg Drokin <oleg.drokin@...el.com>,
Russell King <linux@....linux.org.uk>,
Catalin Marinas <catalin.marinas@....com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RESEND][PATCH v2 0/9] x86: remove cpu_**_mask() functions
On Tue, 19 May 2015, Bartosz Golaszewski wrote:
> Two functions defined in asm/smp.h: cpu_sibling_mask() and cpu_core_mask(),
> have the same functionality as macros defined in linux/topology.h:
> topology_thread_cpumask() and topology_core_cpumask() respectively.
>
> They are not documented and are architecture specific. Also: different
> naming for the same functionality (in case of cpu_sibling_mask() and
> topology_thread_cpumask()) is a bit misleading.
>
> This series makes all the callers switch to using the topology.h macros
> and removes their smp.h counterparts. While we're at it: rename
> topology_thread_cpumask() to topology_sibling_cpumask() to be
> consistent with the term used in the scheduler.
>
> The same duplication exists on powerpc.
>
> NOTE: patch 2/9 had been already submitted separately but didn't
> receive any attention, so I'm attaching it to this series.
As this touches the world and some more, I think it should go through
Andrews mm tree.
Andrew, can you please pick that up?
For the x86 parts: Reviewed-by: Thomas Gleixner <tglx@...utronix.de>
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists