From: Frank Rowand <frowand.list@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org, Rob Herring <robh+dt@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v2 1/1] of: introduce event tracepoints for dynamic device_node lifecyle
Date: Thu, 25 Jan 2018 00:30:39 -0800 [thread overview]
Message-ID: <ba2b76ee-f048-496c-eb3a-b9060b6701b7@gmail.com> (raw)
In-Reply-To: <CAMuHMdVuN5iRLqWuPH_UVR1zDJK-rPHZ6guU-ssPuoZ=UWTAFw@mail.gmail.com>
On 01/25/18 00:01, Geert Uytterhoeven wrote:
> Hi Frank,
>
> On Thu, Jan 25, 2018 at 7:48 AM, Frank Rowand <frowand.list@gmail.com> wrote:
>>> create mode 100644 include/trace/events/of.h
>>
>> mode looks incorrect. Existing files in include/trace/events/ are -rw-rw----
>
> Not in my git clone ;-) 644 should be fine.
>
> Gr{oetje,eeting}s,
>
> Geert
Thanks!!! I just learned something new about git. Now I have to go experiment
a bit to make sure I learned properly.
-Frank
next prev parent reply other threads:[~2018-01-25 8:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 14:31 [RFC PATCH v2 0/1] of: easier debugging for node life cycle issues Wolfram Sang
2018-01-21 14:31 ` [RFC PATCH v2 1/1] of: introduce event tracepoints for dynamic device_node lifecyle Wolfram Sang
2018-01-21 22:01 ` Steven Rostedt
2018-01-25 6:48 ` Frank Rowand
2018-01-25 6:58 ` Frank Rowand
2018-01-25 8:01 ` Geert Uytterhoeven
2018-01-25 8:30 ` Frank Rowand [this message]
2018-01-25 22:40 ` Tyrel Datwyler
2018-01-25 23:31 ` Frank Rowand
2018-01-25 8:32 ` Frank Rowand
2018-01-22 8:43 ` [RFC PATCH v2 0/1] of: easier debugging for node life cycle issues Frank Rowand
2018-01-22 11:49 ` Wolfram Sang
2018-01-23 12:11 ` Michael Ellerman
2018-01-23 19:53 ` Frank Rowand
2018-01-25 6:47 ` Frank Rowand
2018-01-25 23:12 ` Wolfram Sang
2018-01-26 0:42 ` Frank Rowand
2018-01-25 6:48 ` Frank Rowand
2018-01-25 6:55 ` Frank Rowand
2018-01-25 11:03 ` Steven Rostedt
2018-01-25 21:49 ` Frank Rowand
2018-01-25 23:14 ` Wolfram Sang
2018-01-26 0:46 ` Frank Rowand
2018-02-01 17:10 ` Steven Rostedt
2018-01-25 23:53 ` Tyrel Datwyler
2018-01-26 1:08 ` Frank Rowand
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=ba2b76ee-f048-496c-eb3a-b9060b6701b7@gmail.com \
--to=frowand.list@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tyreld@linux.vnet.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).