From: Michael Ellerman <mpe@ellerman.id.au>
To: Vincent Legoll <vincent.legoll@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Vincent Legoll <vincent.legoll@gmail.com>
Subject: Ping Re: [PATCH] virtio: make VIRTIO a menuconfig to ease disabling it all
Date: Tue, 23 Jan 2018 15:31:32 +1100 [thread overview]
Message-ID: <87h8rdp55n.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20180107113356.2806-1-vincent.legoll@gmail.com>
Vincent Legoll <vincent.legoll@gmail.com> writes:
> No need to get into the submenu to disable all VIRTIO-related
> config entries.
>
> This makes it easier to disable all VIRTIO config options
> without entering the submenu. It will also enable one
> to see that en/dis-abled state from the outside menu.
>
> This is only intended to change menuconfig UI, not change
> the config dependencies.
>
> v2: Added "default y" to avoid breaking existing configs
> v3: Fixed wrong indentation, added *-by from Randy
>
> Signed-off-by: Vincent Legoll <vincent.legoll@gmail.com>
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> Tested-by: Randy Dunlap <rdunlap@infradead.org> # works for me
> ---
> drivers/virtio/Kconfig | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
This has been broken in linux-next for ~6 weeks now, can we please merge
this and get it fixed.
cheers
next prev parent reply other threads:[~2018-01-23 4:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 15:26 Vincent Legoll
2017-12-21 6:44 ` Andrei Vagin
2017-12-21 10:53 ` [PATCH] " Michael Ellerman
2017-12-21 16:23 ` Vincent Legoll
2017-12-22 2:12 ` Michael Ellerman
2018-01-02 22:40 ` Michael Ellerman
2018-01-03 9:49 ` [PATCH, v2] virtio: make VIRTIO a menuconfig to ease disabling it Vincent Legoll
2018-01-03 9:49 ` [PATCH] [PATCH] virtio: make VIRTIO a menuconfig to ease disabling it all Vincent Legoll
2018-01-07 3:25 ` Randy Dunlap
2018-01-07 11:33 ` Vincent Legoll
2018-01-23 4:31 ` Michael Ellerman [this message]
2018-01-23 8:08 ` Ping " Vincent Legoll
2018-01-28 10:14 ` Michael Ellerman
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=87h8rdp55n.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rdunlap@infradead.org \
--cc=vincent.legoll@gmail.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
all inboxes | Powered by JetHome®