From: Atish Patra <atishp@rivosinc.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
frank.chang@sifive.com, qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Bin Meng <bin.meng@windriver.com>,
Weiwei Li <liwei1518@gmail.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>
Subject: Re: [PATCH] target/riscv: Add missing include guard in pmu.h
Date: Wed, 21 Feb 2024 13:27:24 -0800 [thread overview]
Message-ID: <56f06a67-3e8a-42e6-a828-f2c833c74ec4@rivosinc.com> (raw)
In-Reply-To: <9df86826-44c2-4816-ae59-189773c51d95@ventanamicro.com>
On 2/20/24 08:20, Daniel Henrique Barboza wrote:
>
>
> On 2/20/24 08:08, frank.chang@sifive.com wrote:
>> From: Frank Chang <frank.chang@sifive.com>
>>
>> Add missing include guard in pmu.h to avoid the problem of double
>> inclusion.
>>
>> Signed-off-by: Frank Chang <frank.chang@sifive.com>
>> ---
>
> Reviewed-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
>
>> target/riscv/pmu.h | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/target/riscv/pmu.h b/target/riscv/pmu.h
>> index 505fc850d3..7c0ad661e0 100644
>> --- a/target/riscv/pmu.h
>> +++ b/target/riscv/pmu.h
>> @@ -16,6 +16,9 @@
>> * this program. If not, see <http://www.gnu.org/licenses/>.
>> */
>> +#ifndef RISCV_PMU_H
>> +#define RISCV_PMU_H
>> +
>> #include "cpu.h"
>> #include "qapi/error.h"
>> @@ -31,3 +34,5 @@ int riscv_pmu_incr_ctr(RISCVCPU *cpu, enum
>> riscv_pmu_event_idx event_idx);
>> void riscv_pmu_generate_fdt_node(void *fdt, uint32_t cmask, char
>> *pmu_name);
>> int riscv_pmu_setup_timer(CPURISCVState *env, uint64_t value,
>> uint32_t ctr_idx);
>> +
>> +#endif /* RISCV_PMU_H */
>
Oops. Thanks for the fix.
Reviewed-by: Atish Patra <atishp@rivosinc.com>
next prev parent reply other threads:[~2024-02-21 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 11:08 [PATCH] target/riscv: Add missing include guard in pmu.h frank.chang
2024-02-20 11:54 ` Philippe Mathieu-Daudé
2024-02-20 16:20 ` Daniel Henrique Barboza
2024-02-21 21:27 ` Atish Patra [this message]
2024-02-23 4:43 ` Alistair Francis
2024-02-23 4:43 ` 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=56f06a67-3e8a-42e6-a828-f2c833c74ec4@rivosinc.com \
--to=atishp@rivosinc.com \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=frank.chang@sifive.com \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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).