From: Marc Zyngier <maz@kernel.org>
To: "\"Chunhui Li (李春辉)\"" <chunhui.li@mediatek.com>
Cc: "lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"\"Hanks Chen (ꐏ┩�)\"" <Hanks.Chen@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"\"Cheng-Yuh Wu (�钦�I)\"" <Cheng-Yuh.Wu@mediatek.com>
Subject: Re: [PATCH] irqchip/gic-v3: Workaround for GIC-700 erratum 2941627
Date: Sun, 09 Jul 2023 09:20:45 +0100 [thread overview]
Message-ID: <877cr98pia.wl-maz@kernel.org> (raw)
In-Reply-To: <ed3c5fe3f7ed42d58d98e77b3513d6eabf2ad6cd.camel@mediatek.com>
On Fri, 07 Jul 2023 13:14:30 +0100,
"Chunhui Li (李春辉)" <chunhui.li@mediatek.com> wrote:
>
> Tested-by: Chunhui Li <chunhui.li@mediatek.com>
You seem to have tested the initial version. but there's a v2 already
posted as a reply to the initial one. Can you please give that one a
go instead?
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: "\"Chunhui Li (李春辉)\"" <chunhui.li@mediatek.com>
Cc: "lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"\"Hanks Chen (ꐏ┩�)\"" <Hanks.Chen@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"\"Cheng-Yuh Wu (�钦�I)\"" <Cheng-Yuh.Wu@mediatek.com>
Subject: Re: [PATCH] irqchip/gic-v3: Workaround for GIC-700 erratum 2941627
Date: Sun, 09 Jul 2023 09:20:45 +0100 [thread overview]
Message-ID: <877cr98pia.wl-maz@kernel.org> (raw)
In-Reply-To: <ed3c5fe3f7ed42d58d98e77b3513d6eabf2ad6cd.camel@mediatek.com>
On Fri, 07 Jul 2023 13:14:30 +0100,
"Chunhui Li (李春辉)" <chunhui.li@mediatek.com> wrote:
>
> Tested-by: Chunhui Li <chunhui.li@mediatek.com>
You seem to have tested the initial version. but there's a v2 already
posted as a reply to the initial one. Can you please give that one a
go instead?
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2023-07-09 8:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 12:14 [PATCH] irqchip/gic-v3: Workaround for GIC-700 erratum 2941627 Chunhui Li (李春辉)
2023-07-09 8:20 ` Marc Zyngier [this message]
2023-07-09 8:20 ` Marc Zyngier
2023-07-10 6:00 ` Chunhui Li (李春辉)
2023-07-10 6:00 ` Chunhui Li (李春辉)
2023-07-11 2:03 ` Chunhui Li (李春辉)
2023-07-11 2:03 ` Chunhui Li (李春辉)
-- strict thread matches above, loose matches on Subject: below --
2023-07-12 1:40 Chunhui Li (李春辉)
2023-07-12 7:21 ` Marc Zyngier
2023-07-12 7:21 ` Marc Zyngier
2023-07-07 11:45 Chunhui Li (李春辉)
2023-07-04 12:34 Lorenzo Pieralisi
2023-07-04 12:34 ` Lorenzo Pieralisi
2023-07-04 14:44 ` Marc Zyngier
2023-07-04 14:44 ` Marc Zyngier
2023-07-04 15:14 ` Lorenzo Pieralisi
2023-07-04 15:14 ` Lorenzo Pieralisi
2023-07-04 15:23 ` Marc Zyngier
2023-07-04 15:23 ` Marc Zyngier
2023-07-04 15:27 ` Lorenzo Pieralisi
2023-07-04 15:27 ` Lorenzo Pieralisi
2023-07-04 15:31 ` Marc Zyngier
2023-07-04 15:31 ` Marc Zyngier
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=877cr98pia.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Cheng-Yuh.Wu@mediatek.com \
--cc=Hanks.Chen@mediatek.com \
--cc=chunhui.li@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.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.