From: Mao Han <han_mao@c-sky.com>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-csky@vger.kernel.org
Subject: Re: [PATCH V6 3/3] riscv: Add support for libdw
Date: Thu, 5 Sep 2019 10:49:41 +0800 [thread overview]
Message-ID: <20190905024940.GB3949@vmh-VirtualBox> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1909041422220.13502@viisi.sifive.com>
On Wed, Sep 04, 2019 at 02:24:57PM -0700, Paul Walmsley wrote:
> Hello Mao Han,
>
> On Thu, 29 Aug 2019, Mao Han wrote:
>
> > This patch add support for DWARF register mappings and libdw registers
> > initialization, which is used by perf callchain analyzing when
> > --call-graph=dwarf is given.
>
> > diff --git a/tools/arch/riscv/include/uapi/asm/perf_regs.h b/tools/arch/riscv/include/uapi/asm/perf_regs.h
> > new file mode 100644
> > index 0000000..df1a581
> > --- /dev/null
> > +++ b/tools/arch/riscv/include/uapi/asm/perf_regs.h
> > @@ -0,0 +1,42 @@
> > +/* SPDX-License-Identifier: GPL-2.0 */
>
> As with
>
> https://lore.kernel.org/linux-riscv/CAJF2gTRXH_bx0rwsTZMTnX+umZfVTL_iVnewPtVM50sLaqJPTg@mail.gmail.com/T/#t
>
> is it possible to change this license string to "GPL-2.0 WITH
> Linux-syscall-note" to match the other Linux architectures?
>
Thanks for suggestion. I didn't notice the UAPI headers are supposed to
have the exception notes. I'll update the license string and resend them.
Thanks,
Mao Han
WARNING: multiple messages have this Message-ID (diff)
From: Mao Han <han_mao@c-sky.com>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-csky@vger.kernel.org
Subject: Re: [PATCH V6 3/3] riscv: Add support for libdw
Date: Thu, 5 Sep 2019 10:49:41 +0800 [thread overview]
Message-ID: <20190905024940.GB3949@vmh-VirtualBox> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1909041422220.13502@viisi.sifive.com>
On Wed, Sep 04, 2019 at 02:24:57PM -0700, Paul Walmsley wrote:
> Hello Mao Han,
>
> On Thu, 29 Aug 2019, Mao Han wrote:
>
> > This patch add support for DWARF register mappings and libdw registers
> > initialization, which is used by perf callchain analyzing when
> > --call-graph=dwarf is given.
>
> > diff --git a/tools/arch/riscv/include/uapi/asm/perf_regs.h b/tools/arch/riscv/include/uapi/asm/perf_regs.h
> > new file mode 100644
> > index 0000000..df1a581
> > --- /dev/null
> > +++ b/tools/arch/riscv/include/uapi/asm/perf_regs.h
> > @@ -0,0 +1,42 @@
> > +/* SPDX-License-Identifier: GPL-2.0 */
>
> As with
>
> https://lore.kernel.org/linux-riscv/CAJF2gTRXH_bx0rwsTZMTnX+umZfVTL_iVnewPtVM50sLaqJPTg@mail.gmail.com/T/#t
>
> is it possible to change this license string to "GPL-2.0 WITH
> Linux-syscall-note" to match the other Linux architectures?
>
Thanks for suggestion. I didn't notice the UAPI headers are supposed to
have the exception notes. I'll update the license string and resend them.
Thanks,
Mao Han
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-09-05 2:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 6:56 [PATCH V6 0/3] riscv: Add perf callchain support Mao Han
2019-08-29 6:56 ` Mao Han
2019-08-29 6:57 ` [PATCH V6 1/3] " Mao Han
2019-08-29 6:57 ` Mao Han
2019-09-04 19:54 ` Paul Walmsley
2019-09-04 19:54 ` Paul Walmsley
2019-09-05 2:30 ` Mao Han
2019-09-05 2:30 ` Mao Han
2019-08-29 6:57 ` [PATCH V6 2/3] riscv: Add support for perf registers sampling Mao Han
2019-08-29 6:57 ` Mao Han
2019-09-04 21:22 ` Paul Walmsley
2019-09-04 21:22 ` Paul Walmsley
2019-08-29 6:57 ` [PATCH V6 3/3] riscv: Add support for libdw Mao Han
2019-08-29 6:57 ` Mao Han
2019-09-04 21:24 ` Paul Walmsley
2019-09-04 21:24 ` Paul Walmsley
2019-09-05 2:49 ` Mao Han [this message]
2019-09-05 2:49 ` Mao Han
2019-09-04 7:25 ` [PATCH V6 0/3] riscv: Add perf callchain support Greentime Hu
2019-09-04 7:25 ` Greentime Hu
2019-09-04 12:20 ` Guo Ren
2019-09-04 12:20 ` Guo Ren
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=20190905024940.GB3949@vmh-VirtualBox \
--to=han_mao@c-sky.com \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=paul.walmsley@sifive.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 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.