From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 4/5] drivers: boot_constraint: Add debugfs support
Date: Thu, 29 Jun 2017 09:41:10 +0530 [thread overview]
Message-ID: <20170629041110.GH29665@vireshk-i7> (raw)
In-Reply-To: <ac877900-52bb-fc97-12cf-3f6099090623@infradead.org>
On 28-06-17, 08:46, Randy Dunlap wrote:
> On 06/28/2017 03:26 AM, Viresh Kumar wrote:
> > This patch adds debugfs support for boot constraints. This is how it
> > looks for a "vmmc-supply" constraint for the MMC device.
> >
>
> Hi,
> Does this build OK when DEBUG_FS is not enabled in kernel .config?
TBH, I haven't tried this earlier as I believed dummy implementation
of all the debugfs helpers is available.
It needs the following debugfs patch (that I sent just now), which
adds the dummy implementation of debugfs_create_ulong().
https://marc.info/?l=linux-kernel&m=149870936319587
--
viresh
next prev parent reply other threads:[~2017-06-29 4:11 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 10:26 [RFC 0/5] drivers: Add boot constraints core Viresh Kumar
2017-06-28 10:26 ` [RFC 1/5] " Viresh Kumar
2017-06-28 15:55 ` Randy Dunlap
2017-06-29 3:51 ` Viresh Kumar
2017-06-29 12:50 ` Russell King - ARM Linux
2017-06-29 14:49 ` Viresh Kumar
2017-06-28 10:26 ` [RFC 2/5] drivers: boot_constraint: Add support for supply constraints Viresh Kumar
2017-06-28 10:26 ` [RFC 3/5] drivers: boot_constraint: Add boot_constraints_disable kernel parameter Viresh Kumar
2017-06-28 15:51 ` Randy Dunlap
2017-06-28 10:26 ` [RFC 4/5] drivers: boot_constraint: Add debugfs support Viresh Kumar
2017-06-28 15:46 ` Randy Dunlap
2017-06-29 4:11 ` Viresh Kumar [this message]
2017-06-28 10:26 ` [RFC 5/5] drivers: Code to test boot constraints Viresh Kumar
2017-06-29 12:40 ` [RFC 0/5] drivers: Add boot constraints core Enrico Weigelt, metux IT consult
2017-06-29 14:47 ` Viresh Kumar
2017-06-29 15:06 ` Enrico Weigelt, metux IT consult
2017-06-30 3:16 ` Viresh Kumar
2017-06-30 3:33 ` Chen-Yu Tsai
2017-06-30 3:55 ` Viresh Kumar
2017-06-30 4:05 ` Chen-Yu Tsai
2017-06-30 4:12 ` Viresh Kumar
2017-06-30 4:22 ` Chen-Yu Tsai
2017-06-30 5:12 ` Viresh Kumar
2017-06-30 6:36 ` Chen-Yu Tsai
2017-06-30 8:43 ` Viresh Kumar
2017-06-30 12:10 ` Mark Brown
2017-07-03 6:15 ` Viresh Kumar
2017-07-03 15:07 ` Mark Brown
2017-07-04 6:45 ` Viresh Kumar
2017-06-30 12:12 ` Mark Brown
2017-06-29 12:49 ` Russell King - ARM Linux
2017-06-29 13:05 ` Enrico Weigelt, metux IT consult
2017-06-29 14:58 ` Viresh Kumar
2017-06-29 15:43 ` Russell King - ARM Linux
2017-06-29 21:00 ` Stephen Boyd
2017-07-05 22:07 ` Rob Clark
2017-07-07 22:39 ` Stephen Boyd
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=20170629041110.GH29665@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@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