kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Diana Craciun <diana.craciun@oss.nxp.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	laurentiu.tudor@nxp.com
Subject: Re: [PATCH v2] vfio/fsl-mc: Fixed vfio-fsl-mc driver compilation on 32 bit
Date: Tue, 13 Oct 2020 13:21:02 -0600	[thread overview]
Message-ID: <20201013132102.57e431ba@w520.home> (raw)
In-Reply-To: <20201013150651.12808-1-diana.craciun@oss.nxp.com>

On Tue, 13 Oct 2020 18:06:51 +0300
Diana Craciun <diana.craciun@oss.nxp.com> wrote:

> The FSL_MC_BUS on which the VFIO-FSL-MC driver is dependent on
> can be compiled on other architectures as well (not only ARM64)
> including 32 bit architectures.
> Include linux/io-64-nonatomic-hi-lo.h to make writeq/readq used
> in the driver available on 32bit platforms.
> 
> Signed-off-by: Diana Craciun <diana.craciun@oss.nxp.com>
> ---
> v1 --> v2
>  - Added prefix to patch description
> 
>  drivers/vfio/fsl-mc/vfio_fsl_mc.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/vfio/fsl-mc/vfio_fsl_mc.c b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> index d009f873578c..80fc7f4ed343 100644
> --- a/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> +++ b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> @@ -13,6 +13,7 @@
>  #include <linux/vfio.h>
>  #include <linux/fsl/mc.h>
>  #include <linux/delay.h>
> +#include <linux/io-64-nonatomic-hi-lo.h>
>  
>  #include "vfio_fsl_mc_private.h"
>  

Thanks, applied and pushed to next.  Hopefully it's either this or the
merge ordering biting us with linux-next.  Thanks,

Alex


      reply	other threads:[~2020-10-13 19:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 15:06 [PATCH v2] vfio/fsl-mc: Fixed vfio-fsl-mc driver compilation on 32 bit Diana Craciun
2020-10-13 19:21 ` Alex Williamson [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=20201013132102.57e431ba@w520.home \
    --to=alex.williamson@redhat.com \
    --cc=diana.craciun@oss.nxp.com \
    --cc=kvm@vger.kernel.org \
    --cc=laurentiu.tudor@nxp.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).