From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
Richard Henderson <rth@twiddle.net>,
qemu-devel@nongnu.org, Marcel Apfelbaum <marcel.a@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/4] s390x/css: Allocate channel_subsys statically
Date: Tue, 23 Feb 2016 12:12:36 +0100 [thread overview]
Message-ID: <20160223121236.6b7fa1dd.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <20160217210312.GF10796@thinpad.lan.raisama.net>
On Wed, 17 Feb 2016 19:03:12 -0200
Eduardo Habkost <ehabkost@redhat.com> wrote:
> On Wed, Feb 17, 2016 at 12:43:13PM +0100, Cornelia Huck wrote:
> > On Tue, 16 Feb 2016 18:59:05 -0200
> > Eduardo Habkost <ehabkost@redhat.com> wrote:
> >
> > > There's no need to use g_malloc0() to allocate the channel_subsys
> > > struct, just use a static variable.
> >
> > The original intention was to model that dynamically somehow, but I
> > don't see that happening anytime soon, so we can just keep it simple.
> >
> > >
> > > Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
> > > Cc: Christian Borntraeger <borntraeger@de.ibm.com>
> > > Cc: Richard Henderson <rth@twiddle.net>
> > > Cc: Alexander Graf <agraf@suse.de>
> > > Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> > > ---
> > > hw/s390x/css.c | 177 ++++++++++++++++++++++++++++-----------------------------
> > > 1 file changed, 88 insertions(+), 89 deletions(-)
> >
> > Seems fine.
> >
> > Should this go through the s390x tree, or will it go through another
> > tree together with the other patches? In any case, have a
> >
> > Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
>
> Thanks!
>
> I was planning to merge it through the (to be created)
> machine-core tree. But it may take some days until I can do that,
> so feel free to merge patches 2-3 through the s390x tree if you
> want to.
>
Applied patches 2&3 to my s390-next branch (with some small
modifications on top of another change I have queued there).
next prev parent reply other threads:[~2016-02-23 11:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 20:59 [Qemu-devel] [PATCH 0/4] machine: Eliminate machine_init()/MODULE_INIT_MACHINE Eduardo Habkost
2016-02-16 20:59 ` [Qemu-devel] [PATCH 1/4] machine: Use type_init() to register machine classes Eduardo Habkost
2016-02-17 15:32 ` Marcel Apfelbaum
2016-02-17 15:57 ` Michael S. Tsirkin
2016-02-18 2:35 ` David Gibson
2016-02-16 20:59 ` [Qemu-devel] [PATCH 2/4] s390x/css: Allocate channel_subsys statically Eduardo Habkost
2016-02-17 11:43 ` Cornelia Huck
2016-02-17 21:03 ` Eduardo Habkost
2016-02-23 11:12 ` Cornelia Huck [this message]
2016-02-16 20:59 ` [Qemu-devel] [PATCH 3/4] s390x/css: Use static initialization for channel_subsys fields Eduardo Habkost
2016-02-17 11:44 ` Cornelia Huck
2016-02-16 20:59 ` [Qemu-devel] [PATCH 4/4] module: Rename machine_init() to opts_init() Eduardo Habkost
2016-02-17 15:36 ` Marcel Apfelbaum
2016-02-17 15:58 ` Michael S. Tsirkin
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=20160223121236.6b7fa1dd.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=ehabkost@redhat.com \
--cc=marcel.a@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).