qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Marcel Apfelbaum <marcel@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PULL v2 0/7] Machine queue, 2018-03-15
Date: Fri, 16 Mar 2018 16:28:54 -0300	[thread overview]
Message-ID: <20180316192854.GM3417@localhost.localdomain> (raw)
In-Reply-To: <CAFEAcA9itE11dUF-Z22M13XT2_sgr0vgDPAsJ_QhUvdT07L5nQ@mail.gmail.com>

On Fri, Mar 16, 2018 at 07:05:29PM +0000, Peter Maydell wrote:
> On 15 March 2018 at 18:14, Eduardo Habkost <ehabkost@redhat.com> wrote:
> > Changes in v2 (v1 was 2018-03-12):
> > * Fix bsd-user build error
> >
> > The following changes since commit 56e8698ffa8aba9f762f980bc21b5340b006f24b:
> >
> >   Merge remote-tracking branch 'remotes/stsquad/tags/pull-travis-speedup-130318-1' into staging (2018-03-15 14:48:09 +0000)
> >
> > are available in the Git repository at:
> >
> >   git://github.com/ehabkost/qemu.git tags/machine-next-pull-request
> >
> > for you to fetch changes up to 7cbb6fd8926b9b590c0725b9b7d0a11db6aefd08:
> >
> >   cpu: drop unnecessary NULL check and cpu_common_class_by_name() (2018-03-15 14:52:40 -0300)
> >
> > ----------------------------------------------------------------
> > Machine queue, 2018-03-15
> >
> 
> Hi. This produces several warning messages running make check:
> 
> WARNING: cpu name for target 'riscv32' isn't defined, add it to cpus_map
> WARNING: cpu name for target 'riscv64' isn't defined, add it to cpus_map

Ouch, another conflict with the commits that added target/riscv
after the original series was submitted.  :(

I will drop all the patches in this pull request except for the
only bug fix there ("pc: correct misspelled CPU model-id for pc
2.2").

Igor, can you resubmit the cpu_model/cpu_type series fixing the
warnings so I can queue it for v2.13?

-- 
Eduardo

  reply	other threads:[~2018-03-16 19:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 18:14 [Qemu-devel] [PULL v2 0/7] Machine queue, 2018-03-15 Eduardo Habkost
2018-03-15 18:14 ` [Qemu-devel] [PULL v2 1/7] pc: correct misspelled CPU model-id for pc 2.2 Eduardo Habkost
2018-03-15 18:14 ` [Qemu-devel] [PULL v2 2/7] nios2: 10m50_devboard: replace cpu_model with cpu_type Eduardo Habkost
2018-03-15 18:14 ` [Qemu-devel] [PULL v2 3/7] tests: add machine 'none' with -cpu test Eduardo Habkost
2018-03-19 15:36   ` [Qemu-devel] [PULL v2 3/7] fixup! " Igor Mammedov
2018-03-15 18:14 ` [Qemu-devel] [PULL v2 4/7] cpu: add CPU_RESOLVING_TYPE macro Eduardo Habkost
2018-03-15 18:14 ` [Qemu-devel] [PULL v2 5/7] Use cpu_create(type) instead of cpu_init(cpu_model) Eduardo Habkost
2018-03-15 18:14 ` [Qemu-devel] [PULL v2 6/7] cpu: get rid of unused cpu_init() defines Eduardo Habkost
2018-03-15 18:14 ` [Qemu-devel] [PULL v2 7/7] cpu: drop unnecessary NULL check and cpu_common_class_by_name() Eduardo Habkost
2018-03-16 19:05 ` [Qemu-devel] [PULL v2 0/7] Machine queue, 2018-03-15 Peter Maydell
2018-03-16 19:28   ` Eduardo Habkost [this message]
2018-03-19 15:01     ` Igor Mammedov
2018-03-19 17:08       ` Eduardo Habkost

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=20180316192854.GM3417@localhost.localdomain \
    --to=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=marcel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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).