linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Rob Clark <robdclark@gmail.com>
Cc: arm@kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm-msm@vger.kernel.org,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	David Brown <davidb@codeaurora.org>,
	Dave Airlie <airlied@redhat.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v2 6/7] drm/msm: Drop unnecessary mach include
Date: Mon, 30 Dec 2013 21:15:58 -0800	[thread overview]
Message-ID: <20131231051558.GB14405@codeaurora.org> (raw)
In-Reply-To: <CAF6AEGt7o65zpPPJa1chvYdp+K-dkSH9Buq=rDxyrUyS0zh3eA@mail.gmail.com>

On 12/30, Rob Clark wrote:
> On Mon, Dec 30, 2013 at 8:12 PM, Rob Clark <robdclark@gmail.com> wrote:
> > On Mon, Dec 30, 2013 at 4:15 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
> >> This file doesn't use the clk_reset() API that is exposed in
> >> mach-msm's mach/clk.h file. Remove the include so that this
> >> driver can be compiled as part of the multi-platform kernel.
> >
> > Thanks!
> >
> > Signed-off-by: Rob Clark <robdclark@gmail.com>

I think you mean Acked-by? Signed-off-by usually means you're
sending the patch along.

> 
> oh, fwiw, things are a bit re-arranged on msm-next-staging (to add
> 8074 and 8060a support).. currently I have:
> 
> ------------------
> #if defined(CONFIG_ARCH_MSM)
> #  include <mach/clk.h>
> #elif defined(CONFIG_COMPILE_TEST)
> /* stubs we need for compile-test: */
> static inline struct device *msm_iommu_get_ctx(const char *ctx_name)
> {
>         return NULL;
> }
> #endif
> ------------------
> 
> Not really sure what to do about msm_iommu_get_ctx(), or whether I
> still need that?
> 

I think the drm Kconfig should be selecting the MSM iommu Kconfig
symbol. At least for now, it's a direct compile time dependency
of this driver. I still don't see a use of mach/clk.h though, so
we should be able to drop it completely.

Is your msm-next-staging tree going into v3.14? I don't see
anything in linux-next so far.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2013-12-31  5:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-30 21:15 [PATCH v2 0/7] Allow MSM DT platforms to be built multi-platform Stephen Boyd
2013-12-30 21:15 ` [PATCH v2 1/7] usb: phy: msm: Move mach dependent code to platform data Stephen Boyd
2013-12-30 21:15 ` [PATCH v2 2/7] mmc: msm_sdcc: Limit driver to platforms that use it Stephen Boyd
2013-12-30 21:15 ` [PATCH v2 3/7] tty: serial: Limit msm_serial_hs " Stephen Boyd
2014-01-02 18:10   ` Arnd Bergmann
2014-01-02 20:20     ` Stephen Boyd
2014-01-02 20:26       ` Arnd Bergmann
2013-12-30 21:15 ` [PATCH v2 4/7] ARM: msm: Only build clock.c on proc_comm based platforms Stephen Boyd
2013-12-30 21:15 ` [PATCH v2 5/7] ARM: msm: Only build timer.c if required Stephen Boyd
2013-12-30 21:15 ` [PATCH v2 6/7] drm/msm: Drop unnecessary mach include Stephen Boyd
2013-12-30 21:20   ` Stephen Boyd
2013-12-31  1:12   ` Rob Clark
2013-12-31  1:19     ` Rob Clark
2013-12-31  5:15       ` Stephen Boyd [this message]
2014-01-09  8:13         ` Olof Johansson
2014-01-09 18:40           ` Stephen Boyd
2013-12-30 21:15 ` [PATCH v2 7/7] ARM: msm: Move MSM's DT based hardware to multi-platform support Stephen Boyd
2013-12-30 21:17 ` [PATCH v2 0/7] Allow MSM DT platforms to be built multi-platform Stephen Boyd
2014-01-02 18:13 ` Arnd Bergmann
2014-01-03 18:51   ` Stephen Boyd
2014-01-03 19:31     ` Olof Johansson
2014-01-09  8:11       ` Olof Johansson

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=20131231051558.GB14405@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=airlied@redhat.com \
    --cc=arm@kernel.org \
    --cc=davidb@codeaurora.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robdclark@gmail.com \
    /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).