From: Greg KH <gregkh@linuxfoundation.org>
To: dann frazier <dann.frazier@canonical.com>
Cc: stable@vger.kernel.org,
Valentin Schneider <valentin.schneider@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Sergei Trofimovich <slyfox@gentoo.org>,
Anatoly Pugachev <matorola@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4.19 0/3] sched/topology: Fix missing scheduling domain levels
Date: Thu, 17 Mar 2022 11:06:29 +0100 [thread overview]
Message-ID: <YjMIJRWklprJMVh4@kroah.com> (raw)
In-Reply-To: <20220316164808.569272-1-dann.frazier@canonical.com>
On Wed, Mar 16, 2022 at 10:48:05AM -0600, dann frazier wrote:
> This is a 4.19.y version of a patch series I submitted earlier for
> 5.4.y/5.10.y.
>
> Change from v1:
> - Fix build failure on ia64 in patch 3/3.
>
Now queued up, again :)
thanks,
greg k-h
prev parent reply other threads:[~2022-03-17 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 16:48 [PATCH v2 4.19 0/3] sched/topology: Fix missing scheduling domain levels dann frazier
2022-03-16 16:48 ` [PATCH v2 4.19 1/3] sched/topology: Make sched_init_numa() use a set for the deduplicating sort dann frazier
2022-03-16 16:48 ` [PATCH v2 4.19 2/3] sched/topology: Fix sched_domain_topology_level alloc in sched_init_numa() dann frazier
2022-03-16 16:48 ` [PATCH v2 4.19 3/3] ia64: ensure proper NUMA distance and possible map initialization dann frazier
2022-03-17 10:06 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YjMIJRWklprJMVh4@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=dann.frazier@canonical.com \
--cc=dietmar.eggemann@arm.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matorola@gmail.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=slyfox@gentoo.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.