From: Rob Herring <robh@kernel.org>
To: Nickhu <nickhu@andestech.com>
Cc: greentime@andestech.com, linux-kernel@vger.kernel.org,
arnd@arndb.de, mark.rutland@arm.com, deanbo422@gmail.com,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, ebiederm@xmission.com, pombredanne@nexb.com,
tglx@linutronix.de, kstewart@linuxfoundation.org,
gregkh@linuxfoundation.org, john.garry@huawei.com,
devicetree@vger.kernel.org, zong@andestech.com,
alankao@andestech.com, green.hu@gmail.com
Subject: Re: [PATCH v3 4/4] nds32: Add document for NDS32 PMU.
Date: Wed, 24 Oct 2018 13:32:48 -0500 [thread overview]
Message-ID: <20181024183247.GA12203@bogus> (raw)
In-Reply-To: <bdfe23ce3ded5299d7b525fcb16c353c2be31924.1540350887.git.nickhu@andestech.com>
On Wed, Oct 24, 2018 at 11:32:40AM +0800, Nickhu wrote:
> The document for how to add NDS32 PMU
> in devicetree.
>
> Signed-off-by: Nickhu <nickhu@andestech.com>
> ---
> Documentation/devicetree/bindings/nds32/pmu.txt | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nds32/pmu.txt
Can you move to bindings/perf/ with other similar h/w. With that,
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-10-24 18:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 3:32 [PATCH v3 0/4] nds32: Perf Support Nickhu
2018-10-24 3:32 ` Nickhu
2018-10-24 3:32 ` [PATCH v3 1/4] nds32: Fix bug in bitfield.h Nickhu
2018-10-24 3:32 ` Nickhu
2018-10-24 3:32 ` [PATCH v3 2/4] nds32: Perf porting Nickhu
2018-10-24 3:32 ` Nickhu
2018-10-24 3:32 ` [PATCH v3 3/4] nds32: Add perf call-graph support Nickhu
2018-10-24 3:32 ` Nickhu
2018-10-24 3:32 ` [PATCH v3 4/4] nds32: Add document for NDS32 PMU Nickhu
2018-10-24 3:32 ` Nickhu
2018-10-24 18:32 ` Rob Herring [this message]
2018-10-25 0:56 ` Nick Hu
2018-10-25 0:56 ` Nick Hu
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=20181024183247.GA12203@bogus \
--to=robh@kernel.org \
--cc=acme@kernel.org \
--cc=alankao@andestech.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=arnd@arndb.de \
--cc=deanbo422@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=ebiederm@xmission.com \
--cc=green.hu@gmail.com \
--cc=greentime@andestech.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nickhu@andestech.com \
--cc=peterz@infradead.org \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=zong@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 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.