From: Markus Armbruster <armbru@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "lvivier@redhat.com" <lvivier@redhat.com>,
"thuth@redhat.com" <thuth@redhat.com>,
"ehabkost@redhat.com" <ehabkost@redhat.com>,
"sw@weilnetz.de" <sw@weilnetz.de>, Tao Xu <tao3.xu@intel.com>,
"Du, Fan" <fan.du@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"mdroth@linux.vnet.ibm.com" <mdroth@linux.vnet.ibm.com>,
"jonathan.cameron@huawei.com" <jonathan.cameron@huawei.com>,
"imammedo@redhat.com" <imammedo@redhat.com>,
"Liu, Jingqi" <jingqi.liu@intel.com>
Subject: Re: [PATCH v20 0/8] Build ACPI Heterogeneous Memory Attribute Table (HMAT)
Date: Tue, 03 Dec 2019 07:00:53 +0100 [thread overview]
Message-ID: <87y2vu7xt6.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20191203003445-mutt-send-email-mst@kernel.org> (Michael S. Tsirkin's message of "Tue, 3 Dec 2019 00:35:30 -0500")
"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Tue, Dec 03, 2019 at 08:53:30AM +0800, Tao Xu wrote:
>> Hi Michael,
>>
>> Could this patch series be queued?
>> Thank you very much!
>>
>> Tao
>
> QEMU is in freeze, so not yet. Please ping after the release.
Just to avoid confusion: it's Michael's personal preference not to
process patches for the next version during freeze. Other maintainers
do, and that's actually the project's policy:
Subject: QEMU Summit 2017: minutes
Message-ID: <CAFEAcA-b9oDkPfZbntWfhWSv1HOnbUf75p_xB_tF74h_NBGPmw@mail.gmail.com>
https://lists.nongnu.org/archive/html/qemu-devel/2017-11/msg04453.html
qemu-next:
* Problem 1: Contributors cannot get patches merged during freeze
(bad experience)
[...]
* Markus Armbruster: Problem 1 is solved if maintainers keep their own
-next trees
* Paolo Bonzini: Maintaining -next could slow down or create work for
-freeze (e.g. who does backports)
* Action: Maintainers mustn't tell submitters to go away just because
we're in a release freeze (it's up to them whether they prefer to
maintain a "-next" tree for their subsystem with patches queued for
the following release, or track which patches they've accepted
some other way)
* We're not going to have an official project-wide "-next" tree, though
Michael, would queuing up patches in a -next branch really be too much
trouble for you?
next prev parent reply other threads:[~2019-12-03 6:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 7:56 [PATCH v20 0/8] Build ACPI Heterogeneous Memory Attribute Table (HMAT) Tao Xu
2019-11-29 7:56 ` [PATCH v20 1/8] numa: Extend CLI to provide initiator information for numa nodes Tao Xu
2019-11-29 7:56 ` [PATCH v20 2/8] numa: Extend CLI to provide memory latency and bandwidth information Tao Xu
2019-11-29 13:11 ` Igor Mammedov
2019-11-29 7:56 ` [PATCH v20 3/8] numa: Extend CLI to provide memory side cache information Tao Xu
2019-11-29 13:24 ` Igor Mammedov
2019-11-29 7:56 ` [PATCH v20 4/8] hmat acpi: Build Memory Proximity Domain Attributes Structure(s) Tao Xu
2019-11-29 7:56 ` [PATCH v20 5/8] hmat acpi: Build System Locality Latency and Bandwidth Information Structure(s) Tao Xu
2019-11-29 7:56 ` [PATCH v20 6/8] hmat acpi: Build Memory Side Cache " Tao Xu
2019-11-29 7:56 ` [PATCH v20 7/8] tests/numa: Add case for QMP build HMAT Tao Xu
2019-11-29 7:56 ` [PATCH v20 8/8] tests/bios-tables-test: add test cases for ACPI HMAT Tao Xu
2019-12-03 0:53 ` [PATCH v20 0/8] Build ACPI Heterogeneous Memory Attribute Table (HMAT) Tao Xu
2019-12-03 5:35 ` Michael S. Tsirkin
2019-12-03 5:46 ` Tao Xu
2019-12-03 6:00 ` Markus Armbruster [this message]
2019-12-03 6:25 ` Michael S. Tsirkin
2019-12-03 6:51 ` Tao Xu
2019-12-03 7:16 ` Markus Armbruster
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=87y2vu7xt6.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fan.du@intel.com \
--cc=imammedo@redhat.com \
--cc=jingqi.liu@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=lvivier@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
--cc=tao3.xu@intel.com \
--cc=thuth@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.