From: Stefan Hajnoczi <stefanha@gmail.com>
To: Richard Henderson <rth@twiddle.net>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PULL for-2.8 0/2] target-alpha update
Date: Tue, 22 Nov 2016 13:08:29 +0000 [thread overview]
Message-ID: <20161122130829.GB483@stefanha-x1.localdomain> (raw)
In-Reply-To: <2aa18a52-2777-0704-57a5-fe0f9726e6b6@twiddle.net>
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
On Tue, Nov 22, 2016 at 08:55:58AM +0100, Richard Henderson wrote:
> On 11/21/2016 08:43 PM, Andreas Schwab wrote:
> > Fetched in submodule path 'roms/qemu-palcode', but it did not contain f3c7e44c70254975df2a00af39701eafbac4d471. Direct fetching of that commit failed.
>
> That's strange. I do see the commit upstream.
>
> https://github.com/rth7680/qemu-palcode/commit/f3c7e44c70254975df2a00af39701eafbac4d471
>
> Is that in fact the origin in your .git/modules/roms/qemu-palcode/config?
I can confirm that everything looks okay from the qemu.git submodule
perspective. The commit is available in the qemu-palcode repo.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-11-22 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 15:02 [Qemu-devel] [PULL for-2.8 0/2] target-alpha update Richard Henderson
2016-11-17 15:02 ` [Qemu-devel] [PULL for-2.8 2/2] target-alpha: Log cpuid with -d int Richard Henderson
2016-11-21 19:43 ` [Qemu-devel] [PULL for-2.8 0/2] target-alpha update Andreas Schwab
2016-11-22 7:55 ` Richard Henderson
2016-11-22 13:08 ` Stefan Hajnoczi [this message]
2016-11-22 18:32 ` Andreas Schwab
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=20161122130829.GB483@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=schwab@linux-m68k.org \
--cc=stefanha@redhat.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).