From: Eric Blake <eblake@redhat.com>
To: Amed Magdy <amagdy.afifi@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
sagark@eecs.berkeley.edu, kbastian@mail.uni-paderborn.de,
palmer@sifive.com, mjc@sifive.com, Alistair.Francis@wdc.com
Subject: Re: [Qemu-devel] [PATCH] riscv: Add proper alignment check and pending 'C' extension upon misa writes
Date: Mon, 25 Feb 2019 08:14:50 -0600 [thread overview]
Message-ID: <b9623b11-0bf9-4dc0-7605-c68601eb1fb5@redhat.com> (raw)
In-Reply-To: <CAKV=O7=JK4t7VxQ74LvjVpM9+TQ6MJ0hA9_XX40ud7OEsh30hQ@mail.gmail.com>
On 2/24/19 2:07 AM, Amed Magdy wrote:
> Thank you so much, Eric.
>
> Sorry about this unclear description.
> I forgot to fix user name in git configuration before submitting the patch.
>
> Sorry about any inconvenience.
Don't worry about it. We were all once first-time contributors, and it
can be a large learning curve.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
WARNING: multiple messages have this Message-ID (diff)
From: Eric Blake <eblake@redhat.com>
To: Amed Magdy <amagdy.afifi@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
sagark@eecs.berkeley.edu, kbastian@mail.uni-paderborn.de,
palmer@sifive.com, mjc@sifive.com, Alistair.Francis@wdc.com
Subject: Re: [Qemu-riscv] [Qemu-devel] [PATCH] riscv: Add proper alignment check and pending 'C' extension upon misa writes
Date: Mon, 25 Feb 2019 08:14:50 -0600 [thread overview]
Message-ID: <b9623b11-0bf9-4dc0-7605-c68601eb1fb5@redhat.com> (raw)
In-Reply-To: <CAKV=O7=JK4t7VxQ74LvjVpM9+TQ6MJ0hA9_XX40ud7OEsh30hQ@mail.gmail.com>
On 2/24/19 2:07 AM, Amed Magdy wrote:
> Thank you so much, Eric.
>
> Sorry about this unclear description.
> I forgot to fix user name in git configuration before submitting the patch.
>
> Sorry about any inconvenience.
Don't worry about it. We were all once first-time contributors, and it
can be a large learning curve.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2019-02-25 14:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 16:25 [Qemu-devel] Add proper alignment check and pending 'C' extension for riscv amagdy.afifi
2019-02-22 16:25 ` [Qemu-riscv] " amagdy.afifi
2019-02-22 16:25 ` [Qemu-devel] [PATCH] riscv: Add proper alignment check and pending 'C' extension upon misa writes amagdy.afifi
2019-02-22 16:25 ` [Qemu-riscv] " amagdy.afifi
2019-02-22 23:57 ` [Qemu-devel] " Richard Henderson
2019-02-22 23:57 ` [Qemu-riscv] " Richard Henderson
2019-02-24 7:57 ` Amed Magdy
2019-02-24 7:57 ` [Qemu-riscv] " Amed Magdy
2019-02-24 19:04 ` Richard Henderson
2019-02-24 19:04 ` [Qemu-riscv] " Richard Henderson
2019-02-26 7:58 ` Amed Magdy
2019-02-26 7:58 ` [Qemu-riscv] " Amed Magdy
2019-02-26 8:11 ` Amed Magdy
2019-02-26 8:11 ` [Qemu-riscv] " Amed Magdy
2019-02-23 21:45 ` Eric Blake
2019-02-23 21:45 ` [Qemu-riscv] " Eric Blake
2019-02-24 8:07 ` Amed Magdy
2019-02-24 8:07 ` [Qemu-riscv] " Amed Magdy
2019-02-25 14:14 ` Eric Blake [this message]
2019-02-25 14:14 ` Eric Blake
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=b9623b11-0bf9-4dc0-7605-c68601eb1fb5@redhat.com \
--to=eblake@redhat.com \
--cc=Alistair.Francis@wdc.com \
--cc=amagdy.afifi@gmail.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=mjc@sifive.com \
--cc=palmer@sifive.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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.