From: Jason Wang <jasowang@redhat.com>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
"Alistair Francis" <Alistair.Francis@wdc.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"Alistair Francis" <alistair23@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] hw: net: cadence_gem: Fix build errors in DB_PRINT()
Date: Thu, 13 Feb 2020 17:42:48 +0800 [thread overview]
Message-ID: <91d39b2d-3077-a638-d253-be9acdb24f8a@redhat.com> (raw)
In-Reply-To: <CAEUhbmUswmWjiaAy+26mYkEMpciTP6u6=WDmVX2U9MKo=uR_qA@mail.gmail.com>
On 2020/2/13 下午5:39, Bin Meng wrote:
> Hi Jason,
>
> On Mon, Aug 19, 2019 at 1:40 PM Jason Wang <jasowang@redhat.com> wrote:
>>
>> On 2019/8/19 下午1:24, Bin Meng wrote:
>>> On Sat, Aug 10, 2019 at 9:58 AM Alistair Francis <alistair23@gmail.com> wrote:
>>>> On Fri, Aug 9, 2019 at 12:26 AM Bin Meng <bmeng.cn@gmail.com> wrote:
>>>>> When CADENCE_GEM_ERR_DEBUG is turned on, there are several
>>>>> compilation errors in DB_PRINT(). Fix them.
>>>>>
>>>>> While we are here, update to use appropriate modifiers in
>>>>> the same DB_PRINT() call.
>>>>>
>>>>> Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
>>>> Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
>>>>
>>> Ping?
>>>
>>> What's the status of this patch?
>>>
>>> Regards,
>>> Bin
>>
>> Applied.
> I checked latest qemu/master and found this patch isn't applied. Could
> you please take a look?
>
> Regards,
> Bin
For some unknown reason it was lost, I've applied in my tree and it will
be in the next pull request.
Sorry.
prev parent reply other threads:[~2020-02-13 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 7:25 [Qemu-devel] [PATCH v3] hw: net: cadence_gem: Fix build errors in DB_PRINT() Bin Meng
2019-08-10 1:57 ` Alistair Francis
2019-08-19 5:24 ` Bin Meng
2019-08-19 5:40 ` Jason Wang
2020-02-13 9:39 ` Bin Meng
2020-02-13 9:42 ` Jason Wang [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=91d39b2d-3077-a638-d253-be9acdb24f8a@redhat.com \
--to=jasowang@redhat.com \
--cc=Alistair.Francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
/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).