From: "jroedel-l3A5Bk7waGM@public.gmane.org" <jroedel-l3A5Bk7waGM@public.gmane.org>
To: Varun Sethi <Varun.Sethi-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: "iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Madalin-Cristian Bucur
<madalin.bucur-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Subject: Re: [iommu:ppc/pamu 1/1] drivers/iommu/fsl_pamu.h:24:32: fatal error: asm/fsl_pamu_stash.h: No such file or directory
Date: Tue, 5 May 2015 15:17:13 +0200 [thread overview]
Message-ID: <20150505131713.GD5438@suse.de> (raw)
In-Reply-To: <BN3PR0301MB12198F55BD2619F392B58AD4EAFC0-CEkquS/Gb81uuip9JPHoc5wN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
Hi Varun,
On Wed, Apr 08, 2015 at 01:24:16PM +0000, Varun Sethi wrote:
> Following issue was observed while building (compile test) for a
> non-powerpc (e500mc) based platform. The pamu driver includes a file
> which is available in the architecture include directory. Should we
> move the header file to general Linux kernel include directory?
Before I added the COMPILE_TEST dependency it looked like this:
depends on PPC_E500MC
Which means the driver was only buildable on e500mc and now you are
telling me that this is broken. What am I missing?
Joerg
next prev parent reply other threads:[~2015-05-05 13:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201503240804.8vcZXNOY%fengguang.wu@intel.com>
[not found] ` <551122E2.1040408@Freescale.com>
[not found] ` <551122E2.1040408-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org>
2015-03-25 5:46 ` [iommu:ppc/pamu 1/1] drivers/iommu/fsl_pamu.h:24:32: fatal error: asm/fsl_pamu_stash.h: No such file or directory Varun Sethi
[not found] ` <BN3PR0301MB12195D8782612E67CDE2BFD9EA0B0-CEkquS/Gb81uuip9JPHoc5wN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2015-03-25 6:11 ` Emil Medve
[not found] ` <55125179.8040801-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org>
2015-03-25 6:25 ` Varun Sethi
[not found] ` <BN3PR0301MB12193C6929AE8CF767B8A78AEA0B0-CEkquS/Gb81uuip9JPHoc5wN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2015-03-25 7:36 ` Emil Medve
[not found] ` <55126585.7040903-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org>
2015-04-08 13:24 ` Varun Sethi
[not found] ` <BN3PR0301MB12198F55BD2619F392B58AD4EAFC0-CEkquS/Gb81uuip9JPHoc5wN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2015-05-05 13:17 ` jroedel-l3A5Bk7waGM [this message]
[not found] ` <20150505131713.GD5438-l3A5Bk7waGM@public.gmane.org>
2015-05-05 13:22 ` Varun Sethi
[not found] ` <BN1PR0301MB06271FBAE46B4CBDD9781D0FEAD10-RQSpjbwlmjSD1ymB6+i1+JwN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2015-05-05 13:42 ` jroedel-l3A5Bk7waGM
[not found] ` <20150505134251.GG5438-l3A5Bk7waGM@public.gmane.org>
2015-05-05 17:57 ` Varun Sethi
[not found] ` <BN1PR0301MB0627F543CF6AE00CFED18B47EAD10-RQSpjbwlmjSD1ymB6+i1+JwN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2015-05-06 8:41 ` joro-zLv9SwRftAIdnm+yROfE0A
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=20150505131713.GD5438@suse.de \
--to=jroedel-l3a5bk7wagm@public.gmane.org \
--cc=Varun.Sethi-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=madalin.bucur-KZfg59tc24xl57MIdRCFDg@public.gmane.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.