From: David Hildenbrand <david@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Igor Kotrasinski <i.kotrasinsk@partner.samsung.com>,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH for-6.0 v1 0/3] softmmu/physmem: shared anonymous memory fixes
Date: Wed, 7 Apr 2021 10:34:19 +0200 [thread overview]
Message-ID: <ba8f7c34-c01f-c1b7-10ee-aef2c10c83bc@redhat.com> (raw)
In-Reply-To: <20210406164643.GJ628002@xz-x1>
On 06.04.21 18:46, Peter Xu wrote:
> On Tue, Apr 06, 2021 at 10:01:23AM +0200, David Hildenbrand wrote:
>> Fixes related to shared anonymous memory, previously sent as part of
>
> The series looks good, but maybe 6.1 material? Since 06329ccecfa ("mem: add
> share parameter to memory-backend-ram", 2018-02-19) is introduced in 2.12.
Thanks, but IIRC, there is no rule that requires bugfixes for fixes only
introduced in this release.
"After the hard feature freeze, the master branch in git is no longer
open for general development. Only bug fixes will be accepted until the
next release."
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-04-07 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 8:01 [PATCH for-6.0 v1 0/3] softmmu/physmem: shared anonymous memory fixes David Hildenbrand
2021-04-06 8:01 ` [PATCH for-6.0 v1 1/3] softmmu/physmem: Mark shared anonymous memory RAM_SHARED David Hildenbrand
2021-04-06 8:01 ` [PATCH for-6.0 v1 2/3] softmmu/physmem: Fix ram_block_discard_range() to handle shared anonymous memory David Hildenbrand
2021-04-06 8:01 ` [PATCH for-6.0 v1 3/3] softmmu/physmem: Fix qemu_ram_remap() " David Hildenbrand
2021-04-06 16:46 ` [PATCH for-6.0 v1 0/3] softmmu/physmem: shared anonymous memory fixes Peter Xu
2021-04-07 8:34 ` David Hildenbrand [this message]
2021-05-25 8:06 ` David Hildenbrand
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=ba8f7c34-c01f-c1b7-10ee-aef2c10c83bc@redhat.com \
--to=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=i.kotrasinsk@partner.samsung.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).