qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Cornelia Huck <cohuck@redhat.com>
Cc: qemu-s390x <qemu-s390x@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 00/54] s390x update
Date: Tue, 21 May 2019 14:53:57 +0100	[thread overview]
Message-ID: <CAFEAcA8QmPYzPeLt5LAg+7x5ySM0x3HUp_o54jo-iObG8ksy+A@mail.gmail.com> (raw)
In-Reply-To: <20190521153104.403980b3.cohuck@redhat.com>

On Tue, 21 May 2019 at 14:31, Cornelia Huck <cohuck@redhat.com> wrote:
>
> On Tue, 21 May 2019 14:24:07 +0100
> Peter Maydell <peter.maydell@linaro.org> wrote:
> > ...it's copying the file into asm-arm/ rather than asm-arm64/.
> > (I did a by-hand move of the file into the right directory and
> > that was sufficient for the compile to succeed.)
>
> I'm obviously not at my best at the moment :(

No big deal, it's always awkward when you don't have access
to the test hardware.

> >
> > Also, can we keep the changes to scripts/ in a separate
> > commit, please? The idea of header-update commits is that they
> > should contain only the changes automatically generated
> > by the script, with no hand-written additions.
>
> This looks a bit like a chicken-and-egg problem, though... without the
> change, we cannot point the script at a current kernel tree. I'd prefer
> the two to stay together, but I can certainly point out the change to
> the script more prominently.

I would structure it as:

Commit 1: update the script
Commit 2: result of running the script

thanks
-- PMM


      reply	other threads:[~2019-05-21 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21  9:20 [Qemu-devel] [PULL v2 00/54] s390x update Cornelia Huck
2019-05-21  9:20 ` [Qemu-devel] [PULL v2 46/54] linux headers: update against Linux 5.2-rc1 Cornelia Huck
2019-05-21 13:24 ` [Qemu-devel] [PULL v2 00/54] s390x update Peter Maydell
2019-05-21 13:31   ` Cornelia Huck
2019-05-21 13:53     ` Peter Maydell [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=CAFEAcA8QmPYzPeLt5LAg+7x5ySM0x3HUp_o54jo-iObG8ksy+A@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=cohuck@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@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).