mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre Ghiti <alex@ghiti.fr>
To: Ben Zong-You Xie <ben717@andestech.com>,
	peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	namhyung@kernel.org, mark.rutland@arm.com,
	alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	irogers@google.com, adrian.hunter@intel.com,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, linux-perf-users@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Cc: dylan@andestech.com, tim609@andestech.com
Subject: Re: [PATCH 0/2] Fix the warnings in the 32-bit platform
Date: Tue, 2 Apr 2024 11:41:17 +0200	[thread overview]
Message-ID: <0643e9d2-3799-4b6b-81fa-fe516e850f72@ghiti.fr> (raw)
In-Reply-To: <20240305120501.1785084-1-ben717@andestech.com>

Hi Ben,

On 05/03/2024 13:04, Ben Zong-You Xie wrote:
> This series fix two incompatible type warnings when building perf in the
> 32-bit platform.
>
> Ben Zong-You Xie (2):
>    perf daemon: Fix the warning about time_t
>    perf riscv: Fix the warning due to the incompatible type
>
>   tools/perf/arch/riscv/util/header.c | 2 +-
>   tools/perf/builtin-daemon.c         | 9 +++++----
>   2 files changed, 6 insertions(+), 5 deletions(-)
>

For the series, you can add:

Reviewed-by: Alexandre Ghiti <alexghiti@rivosinc.com>

To me this should go into -fixes, but which tree? perf or riscv?

Thanks,

Alex


      parent reply	other threads:[~2024-04-02  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 12:04 Ben Zong-You Xie
2024-03-05 12:05 ` [PATCH 1/2] perf daemon: Fix the warning about time_t Ben Zong-You Xie
2024-04-26 17:28   ` Palmer Dabbelt
2024-03-05 12:05 ` [PATCH 2/2] perf riscv: Fix the warning due to the incompatible type Ben Zong-You Xie
2024-04-02  9:41 ` Alexandre Ghiti [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=0643e9d2-3799-4b6b-81fa-fe516e850f72@ghiti.fr \
    --to=alex@ghiti.fr \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=ben717@andestech.com \
    --cc=dylan@andestech.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=peterz@infradead.org \
    --cc=tim609@andestech.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
all inboxes | Powered by JetHome®