From: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Hu Tao <hutao@cn.fujitsu.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
Anton Blanchard <anton@samba.org>,
David Rientjes <rientjes@google.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] Rename nb_numa_nodes to num_numa_nodes
Date: Thu, 3 Jul 2014 09:31:21 -0700 [thread overview]
Message-ID: <20140703163121.GE29053@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140703070310.GC20607@redhat.com>
On 03.07.2014 [10:03:10 +0300], Michael S. Tsirkin wrote:
> On Tue, Jul 01, 2014 at 01:11:08PM -0700, Nishanth Aravamudan wrote:
> > As suggested by Eduardo Habkost, rename nb_numa_nodes to num_numa_nodes
> > throughout the code, as that reflects the use of the variable more
> > clearly.
> >
> > Signed-off-by: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
>
> So far so good but we are past soft freeze. So please keep reposting as
> RFC to avoid noise, and repost without RFC tag after 2.1 is out.
So sorry about that! Will keep RFC for the next post.
Thanks,
Nish
prev parent reply other threads:[~2014-07-03 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 20:11 [Qemu-devel] [PATCH 1/2] Rename nb_numa_nodes to num_numa_nodes Nishanth Aravamudan
2014-07-01 20:13 ` [Qemu-devel] [PATCH 2/2 v5] numa: enable sparse node numbering on ppc Nishanth Aravamudan
2014-07-01 20:39 ` Eduardo Habkost
2014-07-01 20:50 ` Nishanth Aravamudan
2014-07-02 18:21 ` Eduardo Habkost
2014-07-02 21:02 ` Nishanth Aravamudan
2014-07-02 21:52 ` Eduardo Habkost
2014-07-01 20:42 ` [Qemu-devel] [PATCH 1/2] Rename nb_numa_nodes to num_numa_nodes Eduardo Habkost
2014-07-03 7:03 ` Michael S. Tsirkin
2014-07-03 16:31 ` Nishanth Aravamudan [this message]
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=20140703163121.GE29053@linux.vnet.ibm.com \
--to=nacc@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=anton@samba.org \
--cc=ehabkost@redhat.com \
--cc=hutao@cn.fujitsu.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rientjes@google.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.