From: Nishanth Menon <nm@ti.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
<linux-pm@vger.kernel.org>, Aaro Koskinen <aaro.koskinen@iki.fi>,
Tony Lindgren <tony@atomide.com>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Niklas Cassel <nks@flawful.org>, Heiko Stuebner <heiko@sntech.de>,
Kevin Hilman <khilman@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-omap@vger.kernel.org>, <ssantosh@kernel.org>
Subject: Re: [PATCH 3/4] power: avs: smartreflex Move driver to soc specific drivers
Date: Tue, 6 Oct 2020 12:38:03 -0500 [thread overview]
Message-ID: <20201006173803.3xug5pq6zsp23mi6@powwow> (raw)
In-Reply-To: <20201006160516.319830-4-ulf.hansson@linaro.org>
On 18:05-20201006, Ulf Hansson wrote:
> The avs drivers are all SoC specific drivers that doesn't share any code.
> Instead they are located in a directory, mostly to keep similar
> functionality together. From a maintenance point of view, it makes better
> sense to collect SoC specific drivers like these, into the SoC specific
> directories.
>
> Therefore, let's move the smartreflex driver for OMAP to the ti directory.
>
> Cc: Nishanth Menon <nm@ti.com>
> Cc: Aaro Koskinen <aaro.koskinen@iki.fi>
> Cc: Tony Lindgren <tony@atomide.com>
> Cc: linux-omap@vger.kernel.org
> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
[...]
Reviewed-by: Nishanth Menon <nm@ti.com>
CCying Santosh to let him know as well.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2020-10-06 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201006160516.319830-1-ulf.hansson@linaro.org>
2020-10-06 16:05 ` [PATCH 3/4] power: avs: smartreflex Move driver to soc specific drivers Ulf Hansson
2020-10-06 17:38 ` Nishanth Menon [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=20201006173803.3xug5pq6zsp23mi6@powwow \
--to=nm@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=heiko@sntech.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nks@flawful.org \
--cc=rjw@rjwysocki.net \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.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).