From: Igor Mammedov <imammedo@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: peter.maydell@linaro.org, ehabkost@redhat.com, mst@redhat.com,
libvir-list@redhat.com, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, qemu-ppc@nongnu.org, pbonzini@redhat.com,
rth@twiddle.net, david@gibson.dropbear.id.au
Subject: Re: [PATCH] numa: forbid '-numa node, mem' for 5.1 and newer machine types
Date: Fri, 5 Jun 2020 10:33:43 +0200 [thread overview]
Message-ID: <20200605103343.284a4268@redhat.com> (raw)
In-Reply-To: <5a4a1b6b-694c-6814-2ab8-93ba6eaa4b2e@redhat.com>
On Thu, 4 Jun 2020 07:22:51 -0500
Eric Blake <eblake@redhat.com> wrote:
> On 6/2/20 3:41 AM, Igor Mammedov wrote:
> > Deprecation period is run out and it's a time to flip the switch
> > introduced by cd5ff8333a. Disable legacy option for new machine
> > types (since 5.1) and amend documentation.
> >
> > '-numa node,memdev' shall be used instead of disabled option
> > with new machine types.
> >
> > Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> > ---
> > - rebased on top of current master
> > - move compat mode from 4.2 to 5.0
> >
>
> > docs/system/deprecated.rst | 17 -----------------
>
> Lately, when we remove something, we've been moving the documentation
> from 'will be deprecated' to a later section of the document 'has been
> removed', so that the history is not lost. But this diffstat says you
> just deleted, rather than moved, that hunk.
>
I didn't know that,
I'll send v2 with this hunk moved to removed section
prev parent reply other threads:[~2020-06-05 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 8:41 [PATCH] numa: forbid '-numa node, mem' for 5.1 and newer machine types Igor Mammedov
2020-06-04 9:09 ` Michal Privoznik
2020-06-04 12:22 ` Eric Blake
2020-06-05 8:33 ` Igor Mammedov [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=20200605103343.284a4268@redhat.com \
--to=imammedo@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rth@twiddle.net \
/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).