From: "Michael S. Tsirkin" <mst@redhat.com>
To: Shunsuke Mie <mie@igel.co.jp>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
virtualization@lists.linux-foundation.org,
"Eugenio Pérez" <eperezma@redhat.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v2 1/2] virtio_ring: add a struce device forward declaration
Date: Mon, 10 Apr 2023 07:49:38 -0400 [thread overview]
Message-ID: <20230410074929-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230410112845.337212-1-mie@igel.co.jp>
s/struce/struct/ ?
On Mon, Apr 10, 2023 at 08:28:44PM +0900, Shunsuke Mie wrote:
> The virtio_ring header file uses the struct device without a forward
> declaration.
>
> Signed-off-by: Shunsuke Mie <mie@igel.co.jp>
> ---
> include/linux/virtio_ring.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/virtio_ring.h b/include/linux/virtio_ring.h
> index 8b95b69ef694..77a9c2f52919 100644
> --- a/include/linux/virtio_ring.h
> +++ b/include/linux/virtio_ring.h
> @@ -58,6 +58,7 @@ do { \
>
> struct virtio_device;
> struct virtqueue;
> +struct device;
>
> /*
> * Creates a virtqueue and allocates the descriptor ring. If
> --
> 2.25.1
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2023-04-10 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 11:28 [PATCH v2 1/2] virtio_ring: add a struce device forward declaration Shunsuke Mie
2023-04-10 11:28 ` [PATCH v2 2/2] tools/virtio: fix build caused by virtio_ring changes Shunsuke Mie
2023-04-10 12:00 ` Michael S. Tsirkin
2023-04-10 18:40 ` Greg Kroah-Hartman
2023-04-10 19:44 ` Michael S. Tsirkin
2023-04-11 3:25 ` Shunsuke Mie
2023-04-11 6:37 ` Michael S. Tsirkin
2023-04-11 3:17 ` Shunsuke Mie
2023-04-10 11:49 ` Michael S. Tsirkin [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=20230410074929-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=eperezma@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mie@igel.co.jp \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=willy@infradead.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).