qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v4 0/4] hmat acpi: Don't require initiator value in -numa


From: Igor Mammedov
Subject: Re: [PATCH v4 0/4] hmat acpi: Don't require initiator value in -numa
Date: Mon, 4 Jul 2022 11:07:23 +0200

On Fri, 1 Jul 2022 17:08:48 +0100
Jonathan Cameron <Jonathan.Cameron@huawei.com> wrote:

> On Thu, 30 Jun 2022 09:30:58 -0400
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
> 
> > On Thu, Jun 30, 2022 at 02:40:13PM +0200, Brice Goglin 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).    
> > 
> > It's the commit log that's corrupted.
> >   
> > > Do whatever you want with them. I am not allowed to spend more time on 
> > > this.
> > > 
> > > Brice    
> > 
> > Maybe someone will fix up the log and repost. One can hope ..
> >   
> 
> We are planning to send out arm/virt support shortly including a similar test
> that uses this series.  So if no one else gets to it before hand we'll include
> fixed up version of Brice's series with that.

Looking at headers, it looks like patches where sent with Thunderbird
which may corrupted patches (unless special care was taken).
If one would've used 'git send-email', it is likely patches would be fine.


> 
> Jonathan
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]