From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: Fred Griffoul <fgriffo@amazon.co.uk>,
griffoul@gmail.com, kernel test robot <lkp@intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Yi Liu <yi.l.liu@intel.com>,
Kevin Tian <kevin.tian@intel.com>,
Eric Auger <eric.auger@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Christian Brauner <brauner@kernel.org>,
Ankit Agrawal <ankita@nvidia.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Ye Bin <yebin10@huawei.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org
Subject: Re: [PATCH v3 1/2] cgroup/cpuset: export cpuset_cpus_allowed()
Date: Fri, 7 Jun 2024 06:28:57 -1000 [thread overview]
Message-ID: <ZmM1SWBf5rb7P2je@slm.duckdns.org> (raw)
In-Reply-To: <8936c102-725d-4496-b014-cc3edfccf4dd@redhat.com>
On Thu, Jun 06, 2024 at 11:45:37AM -0400, Waiman Long wrote:
>
> On 6/6/24 11:10, Fred Griffoul wrote:
> > A subsequent patch calls cpuset_cpus_allowed() in the vfio driver pci
> > code. Export the symbol to be able to build the vfio driver as a kernel
> > module.
> >
> > Signed-off-by: Fred Griffoul <fgriffo@amazon.co.uk>
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202406060731.L3NSR1Hy-lkp@intel.com/
> > ---
> > kernel/cgroup/cpuset.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
> > index 4237c8748715..9fd56222aa4b 100644
> > --- a/kernel/cgroup/cpuset.c
> > +++ b/kernel/cgroup/cpuset.c
> > @@ -4764,6 +4764,7 @@ void cpuset_cpus_allowed(struct task_struct *tsk, struct cpumask *pmask)
> > rcu_read_unlock();
> > spin_unlock_irqrestore(&callback_lock, flags);
> > }
> > +EXPORT_SYMBOL_GPL(cpuset_cpus_allowed);
> > /**
> > * cpuset_cpus_allowed_fallback - final fallback before complete catastrophe.
>
> LGTM
>
> Acked-by: Waiman Long <longman@redhat.com>
Acked-by: Tejun Heo <tj@kernel.org>
If more convenient, please feel free to route the patch with the rest of the
series. If you want it applied to the cgroup tree, please let me know.
Thanks.
--
tejun
next prev parent reply other threads:[~2024-06-07 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 15:10 [PATCH v3 0/2] vfio/pci: add msi interrupt affinity support Fred Griffoul
2024-06-06 15:10 ` [PATCH v3 1/2] cgroup/cpuset: export cpuset_cpus_allowed() Fred Griffoul
2024-06-06 15:45 ` Waiman Long
2024-06-07 16:28 ` Tejun Heo [this message]
2024-06-07 18:18 ` Frederic Griffoul
2024-06-06 15:10 ` [PATCH v3 2/2] vfio/pci: add msi interrupt affinity support Fred Griffoul
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=ZmM1SWBf5rb7P2je@slm.duckdns.org \
--to=tj@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=ankita@nvidia.com \
--cc=brauner@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=eric.auger@redhat.com \
--cc=fgriffo@amazon.co.uk \
--cc=griffoul@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=lkp@intel.com \
--cc=longman@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=stefanha@redhat.com \
--cc=yebin10@huawei.com \
--cc=yi.l.liu@intel.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