From: Randy Dunlap <randy.dunlap@oracle.com>
To: james_p_freyensee@linux.intel.com
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
sfr@canb.auug.org.au, christophe.guerard@intel.com,
pranav.k.sanghadia@intel.com
Subject: Re: [PATCH] Add PCI config dependency for PTI.
Date: Thu, 7 Jul 2011 14:17:01 -0700 (PDT) [thread overview]
Message-ID: <4E16224D.5040502@oracle.com> (raw)
In-Reply-To: <1310073145-18328-1-git-send-email-james_p_freyensee@linux.intel.com>
On 07/07/11 14:12, james_p_freyensee@linux.intel.com wrote:
> From: J Freyensee <james_p_freyensee@linux.intel.com>
>
> Intel-Atom implementation of PTI will not work with PCI
> configured off, so the pti driver should not be compiled
> in the event someone does not enable PCI in the linux kernel.
>
> Reported-by: Randy Dunlap <randy.dunlap@oracle.com>
> Acked-by: Stephen Rothwell <sfr@canb.auug.org.au>
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Yes, that also.
Thanks.
> Signed-off-by: J Freyensee <james_p_freyensee@linux.intel.com>
> ---
> drivers/misc/Kconfig | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
> index 4e349cd..7fd32a6 100644
> --- a/drivers/misc/Kconfig
> +++ b/drivers/misc/Kconfig
> @@ -146,6 +146,7 @@ config PHANTOM
>
> config INTEL_MID_PTI
> tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
> + depends on PCI
> default n
> help
> The PTI (Parallel Trace Interface) driver directs
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-07-07 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 21:12 [PATCH] Add PCI config dependency for PTI james_p_freyensee
2011-07-07 21:17 ` Randy Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-07 22:02 james_p_freyensee
2011-07-07 22:09 ` Randy Dunlap
2011-07-07 19:24 james_p_freyensee
2011-07-07 19:31 ` Randy Dunlap
2011-07-07 19:59 ` J Freyensee
2011-07-07 20:59 ` Randy Dunlap
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=4E16224D.5040502@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=christophe.guerard@intel.com \
--cc=james_p_freyensee@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pranav.k.sanghadia@intel.com \
--cc=sfr@canb.auug.org.au \
/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).