linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Paul Walmsley <paul.walmsley@sifive.com>
To: Mao Han <han_mao@c-sky.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	christian@brauner.io
Subject: Re: [PATCH V3 0/3] riscv: Add perf callchain support
Date: Fri, 23 Aug 2019 19:12:45 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.9999.1908231910350.18210@viisi.sifive.com> (raw)
In-Reply-To: <20190819105618.GA6377@vmh-VirtualBox>

On Mon, 19 Aug 2019, Mao Han wrote:

> PS: I got some compile error while compiling glibc 2.30 with linux
> v5.3-rc4 header. vfork.S include linux/sched.h(./include/uapi/linux/sched.h)
> which has a struct clone_args inside, added by
> 7f192e3cd316ba58c88dfa26796cf77789dd9872.

Noticed that also.  Probably the sched.h uapi kernel header file needs an 
"#ifndef __ASSEMBLY__" around the struct clone_args...


- Paul

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      reply	other threads:[~2019-08-24  2:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17  8:43 [PATCH V3 0/3] riscv: Add perf callchain support Mao Han
2019-05-17  8:43 ` [PATCH V3 1/3] " Mao Han
2019-05-17  8:43 ` [PATCH V3 2/3] riscv: Add support for perf registers sampling Mao Han
2019-05-17  8:43 ` [PATCH V3 3/3] riscv: Add support for libdw Mao Han
2019-06-03  8:33 ` [PATCH V3 0/3] riscv: Add perf callchain support Mao Han
2019-08-16 17:14 ` Paul Walmsley
2019-08-19  8:18   ` Mao Han
2019-08-19 10:56     ` Mao Han
2019-08-24  2:12       ` Paul Walmsley [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=alpine.DEB.2.21.9999.1908231910350.18210@viisi.sifive.com \
    --to=paul.walmsley@sifive.com \
    --cc=christian@brauner.io \
    --cc=han_mao@c-sky.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.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 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).