From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 00/13] drivers: Boot Constraint core
Date: Thu, 11 Jan 2018 15:21:52 +0530 [thread overview]
Message-ID: <20180111095152.GI3626@vireshk-i7> (raw)
In-Reply-To: <CAOesGMgeaWd5z7VEiVhs=Ei3ZWZQN0C-p4smTMCy3AYrZ-TdTA@mail.gmail.com>
On 10-01-18, 10:54, Olof Johansson wrote:
> The SoC-specific pieces should preferrably go under drivers/soc
> instead, to reduce cross-tree dependencies when introducing new SoC
> variants.
>
> They're more related to the SoC than to the boot_constraint framework anyway.
Hmm, okay.
> Bikeshed: We've traditionally had really terse and precise names under
> drivers/. This is the first verbose one with a _ in it. Maybe find a
> shorter name or just concatenate to 'bootconstraints'? We didn't call
> it remote_proc or rapid_io, etc, either. :)
Sure.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Olof Johansson <olof@lixom.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Rob Clark <robdclark@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Lucas Stach <l.stach@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>, Nishanth Menon <nm@ti.com>,
Xu Wei <xuwei5@hisilicon.com>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH V5 00/13] drivers: Boot Constraint core
Date: Thu, 11 Jan 2018 15:21:52 +0530 [thread overview]
Message-ID: <20180111095152.GI3626@vireshk-i7> (raw)
In-Reply-To: <CAOesGMgeaWd5z7VEiVhs=Ei3ZWZQN0C-p4smTMCy3AYrZ-TdTA@mail.gmail.com>
On 10-01-18, 10:54, Olof Johansson wrote:
> The SoC-specific pieces should preferrably go under drivers/soc
> instead, to reduce cross-tree dependencies when introducing new SoC
> variants.
>
> They're more related to the SoC than to the boot_constraint framework anyway.
Hmm, okay.
> Bikeshed: We've traditionally had really terse and precise names under
> drivers/. This is the first verbose one with a _ in it. Maybe find a
> shorter name or just concatenate to 'bootconstraints'? We didn't call
> it remote_proc or rapid_io, etc, either. :)
Sure.
--
viresh
next prev parent reply other threads:[~2018-01-11 9:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 15:33 [PATCH V5 00/13] drivers: Boot Constraint core Viresh Kumar
2017-12-14 15:33 ` Viresh Kumar
2017-12-14 15:33 ` [PATCH V5 01/13] of: platform: Add of_find_any_device_by_node() Viresh Kumar
2017-12-14 15:33 ` Viresh Kumar
2017-12-14 15:33 ` [PATCH V5 02/13] of: platform: Make of_platform_bus_create() global Viresh Kumar
2017-12-14 15:33 ` Viresh Kumar
2017-12-15 3:58 ` [PATCH V6 " Viresh Kumar
2017-12-15 3:58 ` Viresh Kumar
2017-12-14 15:33 ` [PATCH V5 03/13] drivers: Add boot constraints core Viresh Kumar
2017-12-14 15:33 ` Viresh Kumar
2017-12-14 15:33 ` [PATCH V5 04/13] boot_constraint: Add support for supply constraints Viresh Kumar
2017-12-14 15:33 ` Viresh Kumar
2017-12-14 15:33 ` [PATCH V5 05/13] boot_constraint: Add support for clk constraints Viresh Kumar
2017-12-14 15:33 ` Viresh Kumar
2017-12-14 15:33 ` [PATCH V5 06/13] boot_constraint: Add support for PM constraints Viresh Kumar
2017-12-14 15:33 ` Viresh Kumar
2017-12-14 15:33 ` [PATCH V5 07/13] boot_constraint: Add debugfs support Viresh Kumar
2017-12-14 15:33 ` Viresh Kumar
2017-12-14 15:33 ` [PATCH V5 08/13] boot_constraint: Manage deferrable constraints Viresh Kumar
2017-12-14 15:33 ` Viresh Kumar
2017-12-14 15:33 ` [PATCH V5 09/13] boot_constraint: Add support for Hisilicon platforms Viresh Kumar
2017-12-14 15:33 ` Viresh Kumar
2017-12-14 15:33 ` [PATCH V5 10/13] boot_constraint: Add support for IMX platform Viresh Kumar
2017-12-14 15:33 ` Viresh Kumar
2017-12-14 15:33 ` [PATCH V5 11/13] boot_constraint: Add Qualcomm display controller constraints Viresh Kumar
2017-12-14 15:33 ` Viresh Kumar
2017-12-14 15:33 ` [PATCH V5 12/13] boot_constraint: Update MAINTAINERS Viresh Kumar
2017-12-14 15:33 ` Viresh Kumar
2017-12-14 15:33 ` [PATCH V5 13/13] boot_constraint: Add documentation Viresh Kumar
2017-12-14 15:33 ` Viresh Kumar
2018-01-09 18:47 ` [PATCH V5 00/13] drivers: Boot Constraint core Greg Kroah-Hartman
2018-01-09 18:47 ` Greg Kroah-Hartman
2018-01-10 3:44 ` Viresh Kumar
2018-01-10 3:44 ` Viresh Kumar
2018-01-10 8:08 ` Greg Kroah-Hartman
2018-01-10 8:08 ` Greg Kroah-Hartman
2018-01-10 8:42 ` Viresh Kumar
2018-01-10 8:42 ` Viresh Kumar
2018-01-10 18:19 ` Rob Herring
2018-01-10 18:19 ` Rob Herring
2018-01-10 18:54 ` Olof Johansson
2018-01-10 18:54 ` Olof Johansson
2018-01-11 9:51 ` Viresh Kumar [this message]
2018-01-11 9:51 ` Viresh Kumar
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=20180111095152.GI3626@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 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.