From: Tejun Heo <tj@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Chengming Zhou <zhouchengming@bytedance.com>,
kernel test robot <lkp@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [peterz-queue:sched/psi 11/11] include/linux/cgroup-defs.h:432:38: error: 'NR_PSI_RESOURCES' undeclared here (not in a function)
Date: Wed, 7 Sep 2022 09:38:27 -1000 [thread overview]
Message-ID: <YxjzM9vv55meOAPU@slm.duckdns.org> (raw)
In-Reply-To: <YxjzAnztFtvrtr96@hirez.programming.kicks-ass.net>
On Wed, Sep 07, 2022 at 09:37:38PM +0200, Peter Zijlstra wrote:
> On Wed, Sep 07, 2022 at 05:28:34AM -1000, Tejun Heo wrote:
> > On Wed, Sep 07, 2022 at 10:45:55AM +0800, Chengming Zhou wrote:
> > > 2. This patchset depends on Tejun's commit e2691f6b44ed ("cgroup: Implement cgroup_file_show()") in linux-next
> > >
> > > Maybe peterz-queue should include that first? I don't know what's the normal way to handle.
> >
> > FYI, this patch is in the Greg's driver-core/driver-core-next branch. If
> > it'd be better to route these through the cgroup tree, let me know.
>
> I can base sched/psi off of sched/core and driver-core-next and do a
> separate late pull for it I suppose.
>
> I'm guessing that is more or less what you'd end up doing too, right?
Yeap.
Thanks.
--
tejun
next prev parent reply other threads:[~2022-09-07 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 18:33 kernel test robot
2022-09-07 2:45 ` Chengming Zhou
2022-09-07 8:06 ` Peter Zijlstra
2022-09-07 9:08 ` Chengming Zhou
2022-09-07 15:28 ` Tejun Heo
2022-09-07 19:37 ` Peter Zijlstra
2022-09-07 19:38 ` Tejun Heo [this message]
2022-09-07 19:55 ` Peter Zijlstra
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=YxjzM9vv55meOAPU@slm.duckdns.org \
--to=tj@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=peterz@infradead.org \
--cc=zhouchengming@bytedance.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®