[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190521094543-mutt-send-email-mst@kernel.org>
Date: Tue, 21 May 2019 09:51:35 -0400
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Pankaj Gupta <pagupta@...hat.com>
Cc: linux-nvdimm@...ts.01.org, linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, kvm@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-acpi@...r.kernel.org,
qemu-devel@...gnu.org, linux-ext4@...r.kernel.org,
linux-xfs@...r.kernel.org, dm-devel@...hat.com,
dan.j.williams@...el.com, zwisler@...nel.org,
vishal.l.verma@...el.com, dave.jiang@...el.com,
jasowang@...hat.com, willy@...radead.org, rjw@...ysocki.net,
hch@...radead.org, lenb@...nel.org, jack@...e.cz, tytso@....edu,
adilger.kernel@...ger.ca, darrick.wong@...cle.com,
lcapitulino@...hat.com, kwolf@...hat.com, imammedo@...hat.com,
jmoyer@...hat.com, nilal@...hat.com, riel@...riel.com,
stefanha@...hat.com, aarcange@...hat.com, david@...hat.com,
david@...morbit.com, cohuck@...hat.com,
xiaoguangrong.eric@...il.com, pbonzini@...hat.com,
yuval.shaia@...cle.com, kilobyte@...band.pl, jstaron@...gle.com,
rdunlap@...radead.org, snitzer@...hat.com
Subject: Re: [PATCH v10 2/7] virtio-pmem: Add virtio pmem driver
On Tue, May 21, 2019 at 07:07:08PM +0530, Pankaj Gupta wrote:
> diff --git a/include/uapi/linux/virtio_pmem.h b/include/uapi/linux/virtio_pmem.h
> new file mode 100644
> index 000000000000..7a3e2fe52415
> --- /dev/null
> +++ b/include/uapi/linux/virtio_pmem.h
> @@ -0,0 +1,35 @@
> +/* SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause */
> +/*
> + * Definitions for virtio-pmem devices.
> + *
> + * Copyright (C) 2019 Red Hat, Inc.
> + *
> + * Author(s): Pankaj Gupta <pagupta@...hat.com>
> + */
> +
> +#ifndef _UAPI_LINUX_VIRTIO_PMEM_H
> +#define _UAPI_LINUX_VIRTIO_PMEM_H
> +
> +#include <linux/types.h>
> +#include <linux/virtio_types.h>
> +#include <linux/virtio_ids.h>
> +#include <linux/virtio_config.h>
> +
> +struct virtio_pmem_config {
> + __le64 start;
> + __le64 size;
> +};
> +
config generally should be __u64.
Are you sure sparse does not complain?
> +#define VIRTIO_PMEM_REQ_TYPE_FLUSH 0
> +
> +struct virtio_pmem_resp {
> + /* Host return status corresponding to flush request */
> + __virtio32 ret;
> +};
> +
> +struct virtio_pmem_req {
> + /* command type */
> + __virtio32 type;
> +};
> +
> +#endif
> --
> 2.20.1
Sorry why are these __virtio32 not __le32?
--
MST
Powered by blists - more mailing lists