From: Michael Ellerman <mpe@ellerman.id.au>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: virtualization@lists.linux-foundation.org,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
mst@redhat.com
Subject: Re: [PATCH] virtio: make VIRTIO a menuconfig to ease disabling it all
Date: Fri, 22 Dec 2017 13:12:30 +1100 [thread overview]
Message-ID: <87h8sjpl2p.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <CAEwRq=pVCUPGq4=JLOHQ4gQE0FC+Fotci8+DR_VupgB1BJJB1w@mail.gmail.com>
Vincent Legoll <vincent.legoll@gmail.com> writes:
> Hello,
>
> thanks for the help, and sorry for the poor patch,
>
> On Thu, Dec 21, 2017 at 11:53 AM, Michael Ellerman <mpe@ellerman.id.au> wrote:
>> This breaks all existing .configs *and* defconfigs that use VIRTIO.
>>
>> Please don't do that.
>>
>> If you make it default y then everything will continue to work.
>
> Do you want me to respin it with the added default ?
Yes please, either that or revert it.
cheers
next prev parent reply other threads:[~2017-12-22 2:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171209152657.4762-1-vincent.legoll@gmail.com>
2017-12-21 6:44 ` virtio: make VIRTIO a menuconfig to ease disabling it all Andrei Vagin
2017-12-21 10:53 ` [PATCH] " Michael Ellerman
[not found] ` <87tvwkfj2f.fsf@concordia.ellerman.id.au>
2017-12-21 16:23 ` Vincent Legoll
[not found] ` <CAEwRq=pVCUPGq4=JLOHQ4gQE0FC+Fotci8+DR_VupgB1BJJB1w@mail.gmail.com>
2017-12-22 2:12 ` Michael Ellerman [this message]
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
[not found] ` <20180103094918.6106-1-vincent.legoll@gmail.com>
2018-01-03 9:49 ` [PATCH] [PATCH] virtio: make VIRTIO a menuconfig to ease disabling it all Vincent Legoll
[not found] ` <20180103094918.6106-2-vincent.legoll@gmail.com>
2018-01-07 3:25 ` Randy Dunlap
[not found] <459e2097-f20a-18f8-17d9-2d9ed011211d@infradead.org>
2018-01-07 11:33 ` Vincent Legoll
2017-12-09 15:26 Vincent Legoll
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=87h8sjpl2p.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--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