qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: jrossi@linux.ibm.com, qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: frankja@linux.ibm.com, nsg@linux.ibm.com
Subject: Re: [PATCH 1/5] s390x: Create include files for s390x IPL definitions
Date: Mon, 3 Jun 2024 20:51:13 +0200	[thread overview]
Message-ID: <a7f222a7-f956-4434-917e-161eba330e6c@redhat.com> (raw)
In-Reply-To: <20240529154311.734548-2-jrossi@linux.ibm.com>


  Hi Jared!

On 29/05/2024 17.43, jrossi@linux.ibm.com wrote:
> From: Jared Rossi <jrossi@linux.ibm.com>
> 
> Currently, stuctures defined in both hw/s390x/ipl.h and pc-bios/s390-ccw/iplb.h

Typo: s/stuctures/structures/

> must be kept in sync, which is prone to error. Instead, create a new directory
> at include/hw/s390x/ipl/ to contain the definitions that must be shared.
> 
> Signed-off-by: Jared Rossi <jrossi@linux.ibm.com>
> ---
>   hw/s390x/ipl.h              | 113 +-------------------------------
>   include/hw/s390x/ipl/qipl.h | 126 ++++++++++++++++++++++++++++++++++++
>   pc-bios/s390-ccw/iplb.h     |  84 ++----------------------
>   pc-bios/s390-ccw/Makefile   |   2 +-
>   4 files changed, 133 insertions(+), 192 deletions(-)
>   create mode 100644 include/hw/s390x/ipl/qipl.h
...
> diff --git a/pc-bios/s390-ccw/Makefile b/pc-bios/s390-ccw/Makefile
> index acfcd1e71a..a771439acf 100644
> --- a/pc-bios/s390-ccw/Makefile
> +++ b/pc-bios/s390-ccw/Makefile
> @@ -3,7 +3,7 @@ all: build-all
>   	@true
>   
>   include config-host.mak
> -CFLAGS = -O2 -g
> +CFLAGS = -O2 -g -I $(SRC_PATH)/../..//include/hw/s390x/ipl

Duplicate slash -----------------------^

Apart from these two nits, patch looks fine to me.

  Thomas




  reply	other threads:[~2024-06-03 18:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29 15:43 [PATCH 0/5] s390x: Add Full Boot Order Support jrossi
2024-05-29 15:43 ` [PATCH 1/5] s390x: Create include files for s390x IPL definitions jrossi
2024-06-03 18:51   ` Thomas Huth [this message]
2024-05-29 15:43 ` [PATCH 2/5] s390x: Add loadparm to CcwDevice jrossi
2024-06-04 14:27   ` Thomas Huth
2024-06-04 16:27     ` Jared Rossi
2024-06-04 16:59       ` Thomas Huth
2024-06-05  7:49   ` Thomas Huth
2024-05-29 15:43 ` [PATCH 3/5] s390x: Build IPLB chain for multiple boot devices jrossi
2024-06-03 19:03   ` Thomas Huth
2024-06-04 18:26   ` Thomas Huth
2024-06-05 20:01     ` Jared Rossi
2024-06-07  6:11       ` Thomas Huth
2024-05-29 15:43 ` [PATCH 4/5] s390x: Add boot device fallback infrastructure jrossi
2024-06-05  8:20   ` Thomas Huth
2024-06-05 12:13     ` Thomas Huth
2024-05-29 15:43 ` [PATCH 5/5] s390x: Enable and document boot device fallback on panic jrossi
2024-06-05 13:37   ` Thomas Huth
2024-06-05 14:48     ` Jared Rossi
2024-06-07  5:57       ` Thomas Huth
2024-06-16 23:44         ` Jared Rossi
2024-06-20  8:10           ` Thomas Huth
2024-06-17 14:49     ` Christian Borntraeger
2024-06-20  8:14       ` Thomas Huth
2024-06-04 18:35 ` [PATCH 0/5] s390x: Add Full Boot Order Support Thomas Huth
2024-06-05  8:02 ` Thomas Huth
2024-06-06 19:22   ` Jared Rossi
2024-06-07  6:19     ` Thomas Huth
2024-06-10  3:58       ` Jared Rossi

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=a7f222a7-f956-4434-917e-161eba330e6c@redhat.com \
    --to=thuth@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=jrossi@linux.ibm.com \
    --cc=nsg@linux.ibm.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).