All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org,
	Elena Ufimtseva <elena.ufimtseva@oracle.com>,
	Jagannathan Raman <jag.raman@oracle.com>,
	John G Johnson <john.g.johnson@oracle.com>
Subject: Re: [PATCH] hw/remote/proxy: Categorize Wireless devices as 'Network' ones
Date: Wed, 29 Sep 2021 17:05:36 +0200	[thread overview]
Message-ID: <19cf1682-3436-11b4-ac8d-67841eaef663@vivier.eu> (raw)
In-Reply-To: <20210926201926.1690896-1-f4bug@amsat.org>

Le 26/09/2021 à 22:19, Philippe Mathieu-Daudé a écrit :
> QEMU doesn't distinct network devices per link layer (Ethernet,
> Wi-Fi, CAN, ...). Categorize PCI Wireless cards as Network
> devices.
> 
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
>  hw/remote/proxy.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/hw/remote/proxy.c b/hw/remote/proxy.c
> index 499f540c947..bad164299dd 100644
> --- a/hw/remote/proxy.c
> +++ b/hw/remote/proxy.c
> @@ -324,6 +324,7 @@ static void probe_pci_info(PCIDevice *dev, Error **errp)
>          set_bit(DEVICE_CATEGORY_STORAGE, dc->categories);
>          break;
>      case PCI_BASE_CLASS_NETWORK:
> +    case PCI_BASE_CLASS_WIRELESS:
>          set_bit(DEVICE_CATEGORY_NETWORK, dc->categories);
>          break;
>      case PCI_BASE_CLASS_INPUT:
> 

Applied to my trivial-patches branch.

Thanks,
Laurent


      parent reply	other threads:[~2021-09-29 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26 20:19 [PATCH] hw/remote/proxy: Categorize Wireless devices as 'Network' ones Philippe Mathieu-Daudé
2021-09-27 13:53 ` Jag Raman
2021-09-29 15:05 ` Laurent Vivier [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=19cf1682-3436-11b4-ac8d-67841eaef663@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=elena.ufimtseva@oracle.com \
    --cc=f4bug@amsat.org \
    --cc=jag.raman@oracle.com \
    --cc=john.g.johnson@oracle.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.