From: Stephen Boyd <swboyd@chromium.org>
To: Vaishali Thakkar <vaishali.thakkar@linaro.org>
Cc: Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
Greg KH <gregkh@linuxfoundation.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
rafael@kernel.org, Bjorn Andersson <bjorn.andersson@linaro.org>,
Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH v4 4/5] soc: qcom: socinfo: Expose custom attributes
Date: Mon, 25 Mar 2019 09:01:21 -0700 [thread overview]
Message-ID: <155352968162.20095.9900815050896900150@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <CANNG1HUCvL3=mtitvDZ3fOtt3u5oK7kr=9Nftov71aOsUn3nXA@mail.gmail.com>
Quoting Vaishali Thakkar (2019-03-24 10:42:36)
> On Sat, 23 Mar 2019 at 05:31, Stephen Boyd <swboyd@chromium.org> wrote:
>
> > debugfs_create_devm_seqfile() which may work to print a string from some
> > struct member. I'm not sure why you're using simple_attr_read(). Where
> > does that become important?
>
> DEFINE_DEBUGFS_ATTRIBUTE has simple_attr helpers which
> expects int value. So, in the case of a string it requires to implement
> similar macro and separate helpers for the same.
Why does DEFINE_DEBUGFS_ATTRIBUTE need to be used?
next prev parent reply other threads:[~2019-03-25 16:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 6:50 [PATCH v4 0/5] soc: qcom: Add SoC info driver Vaishali Thakkar
2019-02-25 6:50 ` [PATCH v4 1/5] base: soc: Add serial_number attribute to soc Vaishali Thakkar
2019-02-28 19:23 ` Stephen Boyd
2019-02-28 19:23 ` Stephen Boyd
2019-02-25 6:50 ` [PATCH v4 2/5] base: soc: Export soc_device_register/unregister APIs Vaishali Thakkar
2019-02-28 19:23 ` Stephen Boyd
2019-02-28 19:23 ` Stephen Boyd
2019-03-01 19:08 ` Bjorn Andersson
2019-02-25 6:50 ` [PATCH v4 3/5] soc: qcom: Add socinfo driver Vaishali Thakkar
2019-02-28 19:34 ` Stephen Boyd
2019-02-28 19:34 ` Stephen Boyd
2019-03-01 19:23 ` Bjorn Andersson
2019-02-25 6:50 ` [PATCH v4 4/5] soc: qcom: socinfo: Expose custom attributes Vaishali Thakkar
2019-02-28 21:32 ` Stephen Boyd
2019-02-28 21:32 ` Stephen Boyd
2019-03-14 11:25 ` Vaishali Thakkar
2019-03-14 15:58 ` Stephen Boyd
2019-03-21 5:51 ` Vaishali Thakkar
2019-03-23 0:01 ` Stephen Boyd
2019-03-24 17:42 ` Vaishali Thakkar
2019-03-25 16:01 ` Stephen Boyd [this message]
2019-03-25 20:58 ` Vaishali Thakkar
2019-03-01 19:42 ` Bjorn Andersson
2019-02-25 6:50 ` [PATCH v4 5/5] soc: qcom: socinfo: Expose image information Vaishali Thakkar
2019-02-28 21:34 ` Stephen Boyd
2019-02-28 21:34 ` Stephen Boyd
2019-03-01 19:51 ` Bjorn Andersson
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=155352968162.20095.9900815050896900150@swboyd.mtv.corp.google.com \
--to=swboyd@chromium.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=vaishali.thakkar@linaro.org \
--cc=vkoul@kernel.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 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.