All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: "Lukas Jünger" <lukas.juenger@greensocs.com>
Cc: "Alistair Francis" <alistair.francis@wdc.com>,
	"open list:RISC-V" <qemu-riscv@nongnu.org>,
	"Bin Meng" <bin.meng@windriver.com>,
	mark.burton@greensocs.com,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	luc.michel@greensocs.com
Subject: Re: [PATCH v3 1/2] hw/char: sifive_uart
Date: Tue, 15 Jun 2021 10:19:41 +0800	[thread overview]
Message-ID: <CAEUhbmUXnrXM_-YhjJavG4rDxm1m28XSsQZyd27jeyrNgLELfw@mail.gmail.com> (raw)
In-Reply-To: <20210613141222.548357-2-lukas.juenger@greensocs.com>

On Sun, Jun 13, 2021 at 10:12 PM Lukas Jünger
<lukas.juenger@greensocs.com> wrote:
>
> Make function names consistent
>
> Signed-off-by: Lukas Jünger <lukas.juenger@greensocs.com>
> ---
>  hw/char/sifive_uart.c | 46 ++++++++++++++++++++++---------------------
>  1 file changed, 24 insertions(+), 22 deletions(-)
>

Reviewed-by: Bin Meng <bmeng.cn@gmail.com>


WARNING: multiple messages have this Message-ID (diff)
From: Bin Meng <bmeng.cn@gmail.com>
To: "Lukas Jünger" <lukas.juenger@greensocs.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	"open list:RISC-V" <qemu-riscv@nongnu.org>,
	"Bin Meng" <bin.meng@windriver.com>,
	mark.burton@greensocs.com,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Alistair Francis" <alistair.francis@wdc.com>,
	luc.michel@greensocs.com
Subject: Re: [PATCH v3 1/2] hw/char: sifive_uart
Date: Tue, 15 Jun 2021 10:19:41 +0800	[thread overview]
Message-ID: <CAEUhbmUXnrXM_-YhjJavG4rDxm1m28XSsQZyd27jeyrNgLELfw@mail.gmail.com> (raw)
In-Reply-To: <20210613141222.548357-2-lukas.juenger@greensocs.com>

On Sun, Jun 13, 2021 at 10:12 PM Lukas Jünger
<lukas.juenger@greensocs.com> wrote:
>
> Make function names consistent
>
> Signed-off-by: Lukas Jünger <lukas.juenger@greensocs.com>
> ---
>  hw/char/sifive_uart.c | 46 ++++++++++++++++++++++---------------------
>  1 file changed, 24 insertions(+), 22 deletions(-)
>

Reviewed-by: Bin Meng <bmeng.cn@gmail.com>


  parent reply	other threads:[~2021-06-15  2:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-13 14:12 [PATCH v3 0/2] QOMify Sifive UART Model Lukas Jünger
2021-06-13 14:12 ` Lukas Jünger
2021-06-13 14:12 ` [PATCH v3 1/2] hw/char: sifive_uart Lukas Jünger
2021-06-13 14:12   ` Lukas Jünger
2021-06-14  2:13   ` Alistair Francis
2021-06-14  2:13     ` Alistair Francis
2021-06-15  2:19   ` Bin Meng [this message]
2021-06-15  2:19     ` Bin Meng
2021-06-15  2:22     ` Bin Meng
2021-06-15  2:22       ` Bin Meng
2021-06-13 14:12 ` [PATCH v3 2/2] " Lukas Jünger
2021-06-13 14:12   ` Lukas Jünger
2021-06-15  8:16   ` Alistair Francis
2021-06-15  8:16     ` Alistair Francis

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=CAEUhbmUXnrXM_-YhjJavG4rDxm1m28XSsQZyd27jeyrNgLELfw@mail.gmail.com \
    --to=bmeng.cn@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=bin.meng@windriver.com \
    --cc=luc.michel@greensocs.com \
    --cc=lukas.juenger@greensocs.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mark.burton@greensocs.com \
    --cc=palmer@dabbelt.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@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.