From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
Athira Rajeev <atrajeev@linux.ibm.com>,
jolsa@kernel.org, adrian.hunter@intel.com, irogers@google.com,
linux-perf-users@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
maddy@linux.ibm.com, disgoel@linux.vnet.ibm.com,
hbathini@linux.vnet.ibm.com, Aditya.Bodkhe1@ibm.com,
jiang.peng9@zte.com.cn, Tejas.Manhas1@ibm.com,
sshegde@linux.ibm.com, sfr@canb.auug.org.au,
linux-kernel@vger.kernel.org, mingo@redhat.com,
ravi.bangoria@amd.com, bp@alien8.de
Subject: Re: [PATCH] perf build: Add tools/arch/x86/include/asm/amd/ibs.h to sync the headers
Date: Thu, 24 Apr 2025 13:54:44 -0700 [thread overview]
Message-ID: <aAqlFA4qIVh9SQke@google.com> (raw)
In-Reply-To: <aAqB6kI5mDp4bxY9@x1>
Hello,
On Thu, Apr 24, 2025 at 03:24:42PM -0300, Arnaldo Carvalho de Melo wrote:
> On Thu, Apr 24, 2025 at 10:39:56PM +0530, Venkat Rao Bagalkote wrote:
> > On 24/04/25 10:00 pm, Athira Rajeev wrote:
> > Tested this patch by applying on tip HEAD:
> > 7ab869c799fc0fb22f9b4c2f36aaa603d9c7cc9d and it fixes the reported issue.
>
> This is just a long list of characters, can you please next time provide
> something like, humm, tip/head, not really:
>
> ⬢ [acme@toolbx perf-tools-next]$ git remote -v | grep tip
> tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git (fetch)
> tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git (push)
> ⬢ [acme@toolbx perf-tools-next]$ git remote update tip
> Fetching tip
> ⬢ [acme@toolbx perf-tools-next]$ git show 7ab869c799fc0fb22f9b4c2f36aaa603d9c7cc9d
> fatal: bad object 7ab869c799fc0fb22f9b4c2f36aaa603d9c7cc9d
> ⬢ [acme@toolbx perf-tools-next]$
>
> So please add the summary, that way we can try to figure out if this is
> a rebase and they look for the description instead of this sha1 that I'm
> not finding even after doing a 'git remore update tip'.
Does this mean the kernel change broke the tool build but we don't have
it in the perf-tools-next yet? Then probably we need to wait for the
next merge window to fix it in the tool side, no?
Thanks,
Namhyung
next prev parent reply other threads:[~2025-04-24 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 16:30 [PATCH] perf build: Add tools/arch/x86/include/asm/amd/ibs.h to sync the headers Athira Rajeev
2025-04-24 17:09 ` Venkat Rao Bagalkote
2025-04-24 18:24 ` Arnaldo Carvalho de Melo
2025-04-24 20:54 ` Namhyung Kim [this message]
2025-04-24 21:47 ` Arnaldo Carvalho de Melo
2025-04-25 6:58 ` Venkat Rao Bagalkote
2025-04-24 18:13 ` Arnaldo Carvalho de Melo
2025-04-25 3:06 ` Athira Rajeev
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=aAqlFA4qIVh9SQke@google.com \
--to=namhyung@kernel.org \
--cc=Aditya.Bodkhe1@ibm.com \
--cc=Tejas.Manhas1@ibm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=atrajeev@linux.ibm.com \
--cc=bp@alien8.de \
--cc=disgoel@linux.vnet.ibm.com \
--cc=hbathini@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=jiang.peng9@zte.com.cn \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mingo@redhat.com \
--cc=ravi.bangoria@amd.com \
--cc=sfr@canb.auug.org.au \
--cc=sshegde@linux.ibm.com \
--cc=venkat88@linux.ibm.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).