linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: J Freyensee <james_p_freyensee@linux.intel.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org
Subject: Re: linux-next: Tree for July 4 (misc/pti)
Date: Thu, 07 Jul 2011 09:34:50 -0700	[thread overview]
Message-ID: <4E15E02A.2000005@linux.intel.com> (raw)
In-Reply-To: <20110707093202.a831fce8.randy.dunlap@oracle.com>

On 07/07/2011 09:32 AM, Randy Dunlap wrote:
> On Thu, 07 Jul 2011 09:29:59 -0700 J Freyensee wrote:
>
>> On 07/07/2011 08:14 AM, Randy Dunlap wrote:
>>> On Mon, 4 Jul 2011 13:45:41 -0700 Randy Dunlap wrote:
>>>
>>>> On Mon, 4 Jul 2011 17:09:52 +1000 Stephen Rothwell wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> Changes since 20110701:
>>>> when CONFIG_PCI is not enabled:
>>>>
>>>> drivers/misc/pti.c:410: error: implicit declaration of function 'pci_release_region'
>>>> drivers/misc/pti.c:859: error: implicit declaration of function 'pci_request_region'
>>>>
>>>>
>>>> Stubs for these 2 functions could be added to include/linux/pci.h, but it would
>>>> make more sense to me just to make the driver depend on PCI since it seems to rely
>>>> on so many PCI functions.  or are the PCI pieces optional?
>>> ping.  still a problem in linux-next 20110706.
>> Thanks for the ping.
>>
>> Is there something you need me to do or look at?
>>
>> For Intel-Atom architectures, the MIPI PTI module does sit on the PCI
>> bus.  It's very much dependent upon the PCI bus for working
>> functionality and it's not optional.  So yes, it makes sense for the
>> driver to depend on PCI to be there and if PCI is not enabled on the
>> system, don't build the pti driver.
>>
>> Maybe it's a Kconfig dependency?
> Yes, please send/merge a patch that adds
> 	depends on PCI
> to "config INTEL_MID_PCI".

And just for confirmation, you want me to base this patch on the 
linux-next git tree, correct?

> Thanks.
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2011-07-07 16:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-04  7:09 linux-next: Tree for July 4 Stephen Rothwell
2011-07-04 20:31 ` linux-next: Tree for July 4 (media/radio) Randy Dunlap
2011-07-04 20:45 ` linux-next: Tree for July 4 (misc/pti) Randy Dunlap
2011-07-07 15:14   ` Randy Dunlap
2011-07-07 16:29     ` J Freyensee
2011-07-07 16:32       ` Randy Dunlap
2011-07-07 16:34         ` J Freyensee [this message]
2011-07-07 16:42           ` Randy Dunlap
2011-07-08 20:07         ` Geert Uytterhoeven
2011-07-08 21:24           ` J Freyensee
2011-07-08 21:31             ` 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=4E15E02A.2000005@linux.intel.com \
    --to=james_p_freyensee@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.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).