virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>,
	"Michael S. Tsirkin" <mst@redhat.com>
Cc: stefanha@redhat.com, linux-doc@vger.kernel.org,
	linus.walleij@linaro.org, corbet@lwn.net,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	bgolaszewski@baylibre.com, linux-gpio@vger.kernel.org,
	linux-riscv@lists.infradead.org, msuchanek@suse.de,
	"Enrico Weigelt, metux IT consult" <info@metux.net>
Subject: Re: [PATCH v2 2/2] drivers: gpio: add virtio-gpio guest driver
Date: Wed, 9 Dec 2020 17:31:41 +0800	[thread overview]
Message-ID: <9e11f1ab-6b7c-d50e-d7db-633ebc3d358c@redhat.com> (raw)
In-Reply-To: <500d0c68-0c6d-f5fb-665b-74aec6d59f99@metux.net>


On 2020/12/8 下午3:02, Enrico Weigelt, metux IT consult wrote:
> On 08.12.20 03:36, Jason Wang wrote:
>
> Hi,
>
>> So we endup with two solutions (without a prompt):
>>
>> 1) using select, user may end up with driver without transport
> IMHO not an entirely unusual situation in other places of the kernel,
> eg. one can enable USB devices, w/o having an usb host adapter enabled.
>
> And even if some USB-HA driver is enabled, the actualy machine doesn't
> necessarily have the corresponding device.


Ok, then select works for me.


>
>> 2) using depends, user need to enable at least one transport
>>
>> 2) looks a little bit better I admit.
> So, all virtio devices should depend on TRANSPORT_A || TRANSPORT_B ||
> TRANSPORT_C || ... ? (and also change all these places if another
> transport is added) ?


I think not. The idea is, if none of the transport (select VIRTIO) is 
enabled, user can not enable any virtio drivers (depends on VIRTIO).

Thanks


>
> --mtx
>

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  parent reply	other threads:[~2020-12-09  9:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201203191135.21576-1-info@metux.net>
     [not found] ` <20201203191135.21576-2-info@metux.net>
2020-12-04  3:35   ` [PATCH v2 2/2] drivers: gpio: add virtio-gpio guest driver Jason Wang
     [not found]     ` <96aca1e6-2d5a-deb1-2444-88f938c7a9de@metux.net>
2020-12-05 19:32       ` Michael S. Tsirkin
2020-12-07  3:12         ` Jason Wang
2020-12-07 13:53           ` Michael S. Tsirkin
2020-12-08  2:36             ` Jason Wang
     [not found]               ` <500d0c68-0c6d-f5fb-665b-74aec6d59f99@metux.net>
2020-12-09  9:31                 ` Jason Wang [this message]
     [not found]         ` <e69569b5-0c45-e072-5de4-81a4acecdae3@metux.net>
2020-12-07  3:16           ` Jason Wang
2020-12-07 13:52           ` Michael S. Tsirkin
     [not found]     ` <43f1ee89-89f3-95a3-58f1-7a0a12c2b92f@metux.net>
2020-12-07  3:48       ` Jason Wang
     [not found]         ` <635faeb7-950e-e594-3217-69032ed9cbd1@metux.net>
2020-12-08  2:49           ` Jason Wang
2021-04-13 11:07       ` Alex Bennée
     [not found]   ` <0080d492-2f07-d1c6-d18c-73d4204a5d40@metux.net>
2020-12-08  9:38     ` Howto listen to/handle gpio state changes ? " Linus Walleij
     [not found]       ` <51d3efb7-b7eb-83d7-673a-308dd51616d3@metux.net>
2020-12-09  8:51         ` Linus Walleij
     [not found]           ` <CAK8P3a1PRQGUXkjdSmqxXSONX_ZoCgsfx8hJBUdBUk14tyzErA@mail.gmail.com>
2020-12-09 12:53             ` Linus Walleij
     [not found]   ` <CAOh2x=kcM351ObubnQSzUa=FVBQUmAUhz4u8ExORUthQQ0WbGQ@mail.gmail.com>
     [not found]     ` <253f218d-07ac-1963-75e1-9ac2d035437a@metux.net>
     [not found]       ` <20210526033206.5v362hdywb55msve@vireshk-i7>
2021-07-03  8:05         ` Michael S. Tsirkin
2021-07-05  3:51           ` Viresh Kumar
2020-12-07  9:55 ` [PATCH v2 1/2] drivers: gpio: put virtual gpio device into their own submenu Andy Shevchenko

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=9e11f1ab-6b7c-d50e-d7db-633ebc3d358c@redhat.com \
    --to=jasowang@redhat.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=corbet@lwn.net \
    --cc=info@metux.net \
    --cc=linus.walleij@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lkml@metux.net \
    --cc=mst@redhat.com \
    --cc=msuchanek@suse.de \
    --cc=stefanha@redhat.com \
    --cc=virtualization@lists.linux-foundation.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).