From: "Daniel P. Berrange" <berrange@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: "qemu-devel@nongnu.org qemu-devel" <qemu-devel@nongnu.org>,
Fam Zheng <famz@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v7 0/6] Initial support for keycodemapdb GIT submodule
Date: Fri, 29 Sep 2017 09:54:27 +0100 [thread overview]
Message-ID: <20170929085427.GD6803@redhat.com> (raw)
In-Reply-To: <CDDC4F21-36D9-4341-AE18-B12ABFA4AFBD@gmail.com>
On Thu, Sep 28, 2017 at 08:20:09PM -0400, Programmingkid wrote:
>
> > On Sep 28, 2017, at 12:53 PM, Daniel P. Berrange <berrange@redhat.com> wrote:
> >
> > On Thu, Sep 28, 2017 at 12:47:51PM -0400, Programmingkid wrote:
> >>
> >>> This patch series is an update to:
> >>>
> >>> v1: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02047.html
> >>> v2: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02471.html
> >>> v3: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02517.html
> >>> v4: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02708.html
> >>> v5: https://lists.gnu.org/archive/html/qemu-devel/2017-09/msg02950.html
> >>> v6: https://lists.gnu.org/archive/html/qemu-devel/2017-09/msg07673.html
> >>
> >> <snip>
> >>
> >> These error messages appears when compiling version 7 of this patch series:
> >>
> >> /bin/sh: ./scripts/git-submodule.sh: Permission denied
> >
> > The git diff sets execute permission:
> >
> > diff --git a/scripts/git-submodule.sh b/scripts/git-submodule.sh
> > new file mode 100755
> > index 0000000000..f8e7d44ce6
> > --- /dev/null
> > +++ b/scripts/git-submodule.sh
> >
> > did you use "git am" to apply this series or just plain 'patch', because
> > the latter won't deal with permissions correctly and so would cause that
> > error message above.
>
> I used the patch command. After trying again using 'git am' I was able to built QEMU. Even thought the build did succeed, this error message still appeared:
>
> config-host.mak is out-of-date, running configure
> GIT ui/keycodemapdb dtc
> make: *** No rule to make target `ui/input-keymap-linux-to-qcode.c', needed by `Makefile'. Stop.
> make: *** Waiting for unfinished jobs....
>
> I suggest adding a note to patch 0/7 that states this patch set is best
> applied using 'git am' instead of the patch command. That should help
> someone with testing out this patch set.
*All* patches sent to qemu-devel for review should be applied with
'git am', so there's no need to call it out specially.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-09-29 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4614.1506600439.14748.qemu-devel@nongnu.org>
2017-09-28 16:47 ` [Qemu-devel] [PATCH v7 0/6] Initial support for keycodemapdb GIT submodule Programmingkid
2017-09-28 16:53 ` Daniel P. Berrange
2017-09-29 0:20 ` Programmingkid
2017-09-29 8:54 ` Daniel P. Berrange [this message]
2017-09-28 12:06 Daniel P. Berrange
2017-09-28 12:20 ` no-reply
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=20170929085427.GD6803@redhat.com \
--to=berrange@redhat.com \
--cc=famz@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.com \
--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).