From: Igor Mammedov <imammedo@redhat.com>
To: Brice Goglin <Brice.Goglin@inria.fr>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Liu Jingqi" <jingqi.liu@intel.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Yanan Wang" <wangyanan55@huawei.com>,
"Jonathan Cameron" <jonathan.cameron@huawei.com>,
mst@redhat.com
Subject: Re: [PATCH v4 0/4] hmat acpi: Don't require initiator value in -numa
Date: Thu, 30 Jun 2022 14:56:16 +0200 [thread overview]
Message-ID: <20220630145616.3c070af4@redhat.com> (raw)
In-Reply-To: <17551978-4608-f9e4-8aab-d5d7512dc5a7@inria.fr>
On Thu, 30 Jun 2022 14:40:13 +0200
Brice Goglin <Brice.Goglin@inria.fr> wrote:
> Le 30/06/2022 à 14:23, Igor Mammedov a écrit :
> > On Thu, 30 Jun 2022 09:36:47 +0200
> > Brice Goglin <Brice.Goglin@inria.fr> wrote:
> >
> >> Allow -numa without initiator value when hmat=on so that we may
> >> build more complex topologies, e.g. NUMA nodes whose best initiators
> >> are not just another single node.
> >>
> > patches looks fine code-wise,
> > however something wrong with them, i.e. 'git am' doesn't like them
> > nor ./scripts/checkpatch (which one should use before sending patches).
> >
> > I've checked it's not my mail server/client issue(or whatever)
> > that corrupts them (ones downloaded from patchew are broken as well)
>
>
> I don't know what's going on. These 4 patches are in
> https://github.com/bgoglin/qemu/commits/hmat-noinitiator (rebased on
> master 10mn ago).
I'm not sure if we take patches from directly from git-forges,
I guess it's upto maintainers.
CCing Michael,
since these should go through his tree
>
> Do whatever you want with them. I am not allowed to spend more time on this.
>
> Brice
>
>
>
next prev parent reply other threads:[~2022-06-30 13:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 7:36 [PATCH v4 0/4] hmat acpi: Don't require initiator value in -numa Brice Goglin
2022-06-30 7:40 ` [PATCH v4 1/4] " Brice Goglin
2022-06-30 13:28 ` Michael S. Tsirkin
2022-06-30 7:40 ` [PATCH v4 2/4] tests: acpi: add and whitelist *.hmat-noinitiator expected blobs Brice Goglin
2022-06-30 7:41 ` [PATCH v4 3/4] tests: acpi: q35: add test for hmat nodes without initiators Brice Goglin
2022-06-30 7:41 ` [PATCH v4 4/4] tests: acpi: q35: update expected blobs *.hmat-noinitiators Brice Goglin
2022-06-30 12:23 ` [PATCH v4 0/4] hmat acpi: Don't require initiator value in -numa Igor Mammedov
2022-06-30 12:40 ` Brice Goglin
2022-06-30 12:56 ` Igor Mammedov [this message]
2022-06-30 13:29 ` Michael S. Tsirkin
2022-06-30 13:30 ` Michael S. Tsirkin
2022-07-01 16:08 ` Jonathan Cameron via
2022-07-04 9:07 ` Igor Mammedov
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=20220630145616.3c070af4@redhat.com \
--to=imammedo@redhat.com \
--cc=Brice.Goglin@inria.fr \
--cc=f4bug@amsat.org \
--cc=jingqi.liu@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wangyanan55@huawei.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.