All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Artyom Tarasenko <atar4qemu@gmail.com>
Cc: qemu-devel@nongnu.org, mark.cave-ayland@ilande.co.uk
Subject: Re: [Qemu-devel] [PATCH 2/2] niagara: check if a serial port is available
Date: Tue, 24 Jan 2017 09:25:01 +0100	[thread overview]
Message-ID: <87k29kx3tu.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <1485206573-32452-1-git-send-email-atar4qemu@gmail.com> (Artyom Tarasenko's message of "Mon, 23 Jan 2017 22:22:53 +0100")

Your series lacks threading: the patches don't carry In-Reply-To and
References headers.  The easiest way to fix that is sending them with
git-send-email --thread.  You should be able to omit --thread; it's the
default unless configured otherwise.

Artyom Tarasenko <atar4qemu@gmail.com> writes:

> Reported-by:Markus Armbruster <armbru@redhat.com>
> Signed-off-by: Artyom Tarasenko <atar4qemu@gmail.com>
> ---
>  hw/sparc64/niagara.c | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/hw/sparc64/niagara.c b/hw/sparc64/niagara.c
> index e945b5a..a14724f 100644
> --- a/hw/sparc64/niagara.c
> +++ b/hw/sparc64/niagara.c
> @@ -154,9 +154,10 @@ static void niagara_init(MachineState *machine)
>              exit(1);
>          }
>      }
> -    serial_mm_init(sysmem, NIAGARA_UART_BASE, 0, NULL, 115200,
> -                   serial_hds[0], DEVICE_BIG_ENDIAN);
> -
> +    if (serial_hds[0]) {
> +        serial_mm_init(sysmem, NIAGARA_UART_BASE, 0, NULL, 115200,
> +                       serial_hds[0], DEVICE_BIG_ENDIAN);
> +    }
>      empty_slot_init(NIAGARA_IOBBASE, NIAGARA_IOBSIZE);
>      sun4v_rtc_init(NIAGARA_RTC_BASE);
>  }

Reviewed-by: Markus Armbruster <armbru@redhat.com>

      reply	other threads:[~2017-01-24  8:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 21:22 [Qemu-devel] [PATCH 2/2] niagara: check if a serial port is available Artyom Tarasenko
2017-01-24  8:25 ` Markus Armbruster [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=87k29kx3tu.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=atar4qemu@gmail.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --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.