qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: sellcey@imgtec.com
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Leon Alrae <leon.alrae@imgtec.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Makefile: fix build when VPATH is outside GIT tree
Date: Mon, 28 Sep 2015 10:47:05 +0200	[thread overview]
Message-ID: <5608FE89.6000902@redhat.com> (raw)
In-Reply-To: <1443216251.8687.61.camel@ubuntu-sellcey>



On 25/09/2015 23:24, Steve Ellcey wrote:
> On Fri, 2015-09-18 at 13:40 +0200, Paolo Bonzini wrote:
> 
> > > The problem is due to the fact that some sub directory deps
> > > were listed against SOFTMMU_SUBDIR_RULES instead of SUBDIR_RULES,
> > > so were only processed for system emulators, not user emalutors.
> > > 
> > > Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> > 
> > Queued, thanks.
> 
> Is being queued a status for qemu patches or does that just mean it is
> in your personal queue to handle when you have time?

It's both.  I handle patches that fall through the cracks between
maintained areas (which includes the build system, as it has no formal
maintainer).  So if it's "queued" that means that the submitter need not
care about it anymore, as the patch is in my hands now.

I tend to flush the queue pretty often, around once a week.  The patch
is now in.

Paolo

> I would like to remove my local patch for this and go back to using the
> top-of-tree sources, but it doesn't look like this change has been
> checked in yet.  It does fix my build problem.

      reply	other threads:[~2015-09-28  8:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18 10:01 [Qemu-devel] [PATCH] Makefile: fix build when VPATH is outside GIT tree Daniel P. Berrange
2015-09-18 11:40 ` Paolo Bonzini
2015-09-25 21:24   ` Steve Ellcey
2015-09-28  8:47     ` Paolo Bonzini [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=5608FE89.6000902@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=leon.alrae@imgtec.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sellcey@imgtec.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 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).