From: Thomas Gleixner <tglx@linutronix.de>
To: Irina Tirdea <irina.tirdea@intel.com>
Cc: linux-clk@vger.kernel.org, x86@kernel.org,
Stephen Boyd <sboyd@codeaurora.org>,
Ingo Molnar <mingo@redhat.com>,
Michael Turquette <mturquette@baylibre.com>,
"H. Peter Anvin" <hpa@zytor.com>,
alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Takashi Iwai <tiwai@suse.com>,
Pierre-Louis Bossart <pierre-louis.bossart@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Darren Hart <dvhart@infradead.org>
Subject: Re: [RESEND PATCH v4] clk: x86: Add Atom PMC platform clocks
Date: Thu, 20 Oct 2016 23:52:38 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1610202349200.4938@nanos> (raw)
In-Reply-To: <1476735320-4315-1-git-send-email-irina.tirdea@intel.com>
On Mon, 17 Oct 2016, Irina Tirdea wrote:
> The patch has already been reviewed by Stephen Boyd [1].
> The only remaining question is the one pointed out by Stephen:
> "Will there be problems if this merges through clk tree? If so we
> could take the clk driver part and the platform data include part
> could be duplicated into both trees. Or clk tree could be pulled
> into x86?" [1]
The proper thing to do is:
Move all that cruft including arch/x86/platform/atom/pmc_atom.c into
drivers/platform/x86. There is nothing architecture specific in these
files. It's pure peripheral driver enablement. So drivers/platform/x86 is
the proper location for this. Please discuss this with Darren Hart (cc'ed).
Thanks,
tglx
next prev parent reply other threads:[~2016-10-20 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 20:15 [RESEND PATCH v4] clk: x86: Add Atom PMC platform clocks Irina Tirdea
2016-10-20 21:52 ` Thomas Gleixner [this message]
2016-10-21 4:59 ` Darren Hart
2016-10-24 13:38 ` Tirdea, Irina
2016-10-26 21:33 ` Darren Hart
2016-10-26 21:43 ` Thomas Gleixner
2016-10-26 22:02 ` Darren Hart
2016-10-27 13:50 ` Tirdea, Irina
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=alpine.DEB.2.20.1610202349200.4938@nanos \
--to=tglx@linutronix.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dvhart@infradead.org \
--cc=hpa@zytor.com \
--cc=irina.tirdea@intel.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mturquette@baylibre.com \
--cc=pierre-louis.bossart@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sboyd@codeaurora.org \
--cc=tiwai@suse.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox