From: Paolo Pisati <p.pisati@gmail.com>
To: Andy Gross <andy.gross@linaro.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Paolo Pisati <p.pisati@gmail.com>,
Rajendra Nayak <rnayak@codeaurora.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] dts patches for qcom tsens support
Date: Thu, 25 Aug 2016 14:21:14 +0200 [thread overview]
Message-ID: <20160825122114.GA13196@harukaze> (raw)
In-Reply-To: <CAPBZ5Qdy2kf+xRC9f7ndE3GdJx0HyCabJWxyaYDbZ50HCj82Bg@mail.gmail.com>
On Wed, Aug 24, 2016 at 10:21:17PM -0500, Andy Gross wrote:
>
> Yeah this appears to be the case. So I guess the response is 'don't
> do that'. At least don't cat or od the file. You need to seek and
> read.
True, but the dev file is user readable and any user can trigger it (or
any regression test that rummage among dev files looking for bugs).
--
bye,
p.
prev parent reply other threads:[~2016-08-25 12:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 5:18 [PATCH v3 0/5] dts patches for qcom tsens support Rajendra Nayak
2016-08-17 5:18 ` [PATCH v3 1/5] arm: dts: msm8974: Add thermal zones, tsens and qfprom nodes Rajendra Nayak
2016-08-17 5:18 ` [PATCH v3 2/5] arm: dts: apq8064: " Rajendra Nayak
2016-08-17 5:18 ` [PATCH v3 3/5] arm: dts: apq8084: " Rajendra Nayak
2016-08-17 5:18 ` [PATCH v3 4/5] arm64: dts: msm8916: " Rajendra Nayak
2016-08-17 5:18 ` [PATCH v3 5/5] arm64: dts: msm8996: " Rajendra Nayak
2016-08-17 19:33 ` [PATCH v3 0/5] dts patches for qcom tsens support Andy Gross
[not found] ` <20160817193340.GA18215-3KkwrOJo9xYlRp7syxWybdHuzzzSOjJt@public.gmane.org>
2016-08-24 10:22 ` Paolo Pisati
2016-08-24 12:18 ` Nayak, Rajendra
[not found] ` <57BD90A3.3000106-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-08-24 22:03 ` Andy Gross
2016-08-25 3:13 ` Bjorn Andersson
2016-08-25 3:21 ` Andy Gross
2016-08-25 12:21 ` Paolo Pisati [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=20160825122114.GA13196@harukaze \
--to=p.pisati@gmail.com \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rnayak@codeaurora.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).