All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: J Freyensee <james_p_freyensee@linux.intel.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	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: Fri, 08 Jul 2011 14:31:23 -0700	[thread overview]
Message-ID: <4E17772B.3060906@oracle.com> (raw)
In-Reply-To: <4E17757C.5030909@linux.intel.com>

On 07/08/11 14:24, J Freyensee wrote:
> On 07/08/2011 01:07 PM, Geert Uytterhoeven wrote:
>> On Thu, Jul 7, 2011 at 18:32, Randy Dunlap<randy.dunlap@oracle.com> 
>> 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:
>>>>>>> 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".
>> http://kisskb.ellerman.id.au/kisskb/buildresult/4292241/:
> I can't access that http site (with or without the ':').

Works for me (without the trailing colon).

>> drivers/misc/pti.c:249: error: implicit declaration of function 'kmalloc'
>> drivers/misc/pti.c:258: error: implicit declaration of function 'kfree'
>> drivers/misc/pti.c:657: error: implicit declaration of function
>> 'copy_from_user'
>> drivers/misc/pti.c:848: error: implicit declaration of function 'kzalloc'
>>
>> Probably missing
> 
>>
>> #include<linux/slab.h>
>> #include<linux/uaccess.h>
> 
> I can send a patch to add these two includes.  It didn't have previous
> troubles compiling, so maybe one of the other includes used to be
> including these?


That URL (above) says:
Compiler:  	m68k (m68k-linux-gcc (GCC) 4.4.0)

and different $ARCH-es do different #inclusions.

Anyway, the interfaces are used so the source file should #include
the header files.

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

      reply	other threads:[~2011-07-08 21:31 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
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 [this message]

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=4E17772B.3060906@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=geert@linux-m68k.org \
    --cc=james_p_freyensee@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 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.