All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	James Hogan <jhogan@kernel.org>
Subject: Re: [Qemu-devel] [PATCH v6 0/3] linux-headers: arch fixups
Date: Mon, 14 May 2018 21:29:11 +0300	[thread overview]
Message-ID: <20180514212856-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAFEAcA_bWJupL7oj=uxNAi3=1RGUZxpEeKx1L=JBZa6J4CuuYA@mail.gmail.com>

On Mon, May 14, 2018 at 04:10:42PM +0100, Peter Maydell wrote:
> On 14 May 2018 at 14:07, Michael S. Tsirkin <mst@redhat.com> wrote:
> > It turns out that we have unistd.h and kvm headers for some
> > architectures but not others.  We are thus unable to use e.g. usefaultfd
> > on these systems unless system headers have been updated.
> >
> > Fix up update-linux-headers.sh to make sure we auto-updates
> > all architectures which have linux-headers/
> > (unfortunately this still does not mean "all linux systems").
> >
> > Tested on x86 only.
> >
> > Pls consider merging this through the ARM tree.
> >
> > Changes from v5:
> >     rebase to master
> 
> Still doesn't apply:

Against which commit?

> e104462:xenial:qemu$ patches apply -s
> id:1526303228-486609-1-git-send-email-mst@redhat.com
> Applying: update-linux-headers.sh: unistd.h, kvm consistency
> error: sha1 information is lacking or useless (scripts/update-linux-headers.sh).
> error: could not build fake ancestor
> Patch failed at 0001 update-linux-headers.sh: unistd.h, kvm consistency
> Use 'git am --show-current-patch' to see the failed patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
> e104462:xenial:qemu$ patch --dry-run -p1 <.git/rebase-apply/patch
> checking file scripts/update-linux-headers.sh
> Hunk #1 succeeded at 83 (offset -1 lines).
> Hunk #2 FAILED at 94.
> Hunk #3 FAILED at 124.
> 2 out of 3 hunks FAILED
> 
> The copy of this script in master has code relating to kvm_para.h,
> and whatever you've based this patchset on apparently does not,
> hence the conflicts.
> 
> thanks
> -- PMM

  reply	other threads:[~2018-05-14 18:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 13:07 [Qemu-devel] [PATCH v6 0/3] linux-headers: arch fixups Michael S. Tsirkin
2018-05-14 13:07 ` [Qemu-devel] [PATCH v6 1/3] update-linux-headers.sh: unistd.h, kvm consistency Michael S. Tsirkin
2018-05-14 13:07 ` [Qemu-devel] [PATCH v6 2/3] linux-headers: add unistd.h on all arches Michael S. Tsirkin
2018-05-14 13:07 ` [Qemu-devel] [PATCH v6 3/3] linux-headers: add kvm header for mips Michael S. Tsirkin
2018-05-14 15:10 ` [Qemu-devel] [PATCH v6 0/3] linux-headers: arch fixups Peter Maydell
2018-05-14 18:29   ` Michael S. Tsirkin [this message]
2018-05-14 18:37     ` Peter Maydell
2018-05-14 18:41       ` Michael S. Tsirkin
2018-05-15 13:12       ` Michael S. Tsirkin

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=20180514212856-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=jhogan@kernel.org \
    --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 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.