From: Cornelia Huck <cohuck@redhat.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Eric Farman <farman@linux.ibm.com>,
Vineeth Vijayan <vneethv@linux.ibm.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vfio-ccw: Fix a build error due to missing include of linux/slab.h
Date: Fri, 3 Jul 2020 11:45:27 +0200 [thread overview]
Message-ID: <20200703114527.790ffb82.cohuck@redhat.com> (raw)
In-Reply-To: <20200703022628.6036-1-sean.j.christopherson@intel.com>
On Thu, 2 Jul 2020 19:26:28 -0700
Sean Christopherson <sean.j.christopherson@intel.com> wrote:
> Include linux/slab.h to fix a build error due to kfree() being undefined.
>
> Fixes: 3f02cb2fd9d2d ("vfio-ccw: Wire up the CRW irq and CRW region")
> Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
> ---
>
> Encountered this when cross-compiling with a pretty minimal config, didn't
> bother digging into why the error only showed up in my environment.
>
> drivers/s390/cio/vfio_ccw_chp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/s390/cio/vfio_ccw_chp.c b/drivers/s390/cio/vfio_ccw_chp.c
> index a646fc81c872..13b26a1c7988 100644
> --- a/drivers/s390/cio/vfio_ccw_chp.c
> +++ b/drivers/s390/cio/vfio_ccw_chp.c
> @@ -8,6 +8,7 @@
> * Eric Farman <farman@linux.ibm.com>
> */
>
> +#include <linux/slab.h>
> #include <linux/vfio.h>
> #include "vfio_ccw_private.h"
>
Thanks, applied.
prev parent reply other threads:[~2020-07-03 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 2:26 [PATCH] vfio-ccw: Fix a build error due to missing include of linux/slab.h Sean Christopherson
2020-07-03 9:45 ` Cornelia Huck [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=20200703114527.790ffb82.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=sean.j.christopherson@intel.com \
--cc=vneethv@linux.ibm.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