From: Tao Xu <tao3.xu@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Markus Armbruster <armbru@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>, "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, 3 Dec 2019 14:51:06 +0800 [thread overview]
Message-ID: <d3c4b107-45c7-ff8e-a4e2-92babcfa96bd@intel.com> (raw)
In-Reply-To: <20191203010755-mutt-send-email-mst@kernel.org>
On 12/3/2019 2:25 PM, Michael S. Tsirkin wrote:
> On Tue, Dec 03, 2019 at 07:00:53AM +0100, Markus Armbruster wrote:
>> "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?
>
> Thanks for pointing this out!
>
> I stopped asking for re-post since awhile ago. I don't queue patches in
> a public tree but I do review and do keep track of pending patches.
>
> I tend to ask contributors to also ping because sometimes there's a
> problem with rebase, I drop the patch but forget to tell the
> contributor, and it tends to happen more with big patchsets posted during
> freeze as there's a rush to merge changes right after that.
> I usually don't bother people with this for small patches though.
>
> I'll try to be clearer in my communication so contributors don't feel
> stressed.
>
> Would something like:
>
> "I'll queue it for merge after the release. If possible please ping me
> after the release to help make sure it didn't get dropped."
>
> be clearer?
>
> Hopefully windows CI efforts will soon bear fruit to the point where
> they stress PCI enough to make maintaining next worth the effort.
>
I see. Thanks for Markus and Michael's kindly response. I feel happy
rather than stressed in QEMU community :)
next prev parent reply other threads:[~2019-12-03 6:53 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
2019-12-03 6:25 ` Michael S. Tsirkin
2019-12-03 6:51 ` Tao Xu [this message]
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=d3c4b107-45c7-ff8e-a4e2-92babcfa96bd@intel.com \
--to=tao3.xu@intel.com \
--cc=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=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 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).