[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Yxj3RN9SXl6Azs7G@hirez.programming.kicks-ass.net>
Date: Wed, 7 Sep 2022 21:55:48 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Tejun Heo <tj@...nel.org>
Cc: Chengming Zhou <zhouchengming@...edance.com>,
kernel test robot <lkp@...el.com>,
Johannes Weiner <hannes@...xchg.org>, kbuild-all@...ts.01.org,
linux-kernel@...r.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)
On Wed, Sep 07, 2022 at 09:38:27AM -1000, Tejun Heo wrote:
> 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.
OK, I just pushed out a new sched/psi which is based on a combination of
sched/core and driver-core-next. Lets see if the robots have more
complaints ;-)
Powered by blists - more mailing lists