public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Daniel Mack <daniel@zonque.org>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/3] ARM: pxa: pxa_cplds: add lubbock and mainstone IO
Date: Sun, 26 Apr 2015 21:38:38 +0200	[thread overview]
Message-ID: <87iocillxd.fsf@belgarion.home> (raw)
In-Reply-To: <1430075422.2927.131.camel@x220> (Paul Bolle's message of "Sun, 26 Apr 2015 21:10:22 +0200")

Paul Bolle <pebolle@tiscali.nl> writes:

> On Sat, 2015-04-25 at 23:13 +0200, Robert Jarzmik wrote:
>> --- a/arch/arm/mach-pxa/Kconfig
>> +++ b/arch/arm/mach-pxa/Kconfig
>  
>> +config PXA_SYSTEMS_CPLDS
>> +	bool "Motherboard cplds"
>> +	def_bool ARCH_LUBBOCK || MACH_MAINSTONE
>
> Just
> 	default ARCH_LUBBOCK || MACH_MAINSTONE
>
> should be enough.
Actually this will become a tristate, and I'll take your "default"
suggestion. For v2.

>> +	select MFD_CORE
Ah this is an oversight now I see it. In the move from drivers/mfd to arch/arm I
forgot to remove this. For v2 also.

>> +	help
>> +	  This driver supports the Lubbock and Mainstone multifunction chip
>> +	  found on the pxa25x development platform system (Lubbock) and pxa27x
>> +	  development platform system (Mainstone). This IO board supports the
>> +	  interrupts handling, ethernet controller, flash chips, etc ...
>
>> --- a/arch/arm/mach-pxa/Makefile
>> +++ b/arch/arm/mach-pxa/Makefile
>  
>> +obj-$(CONFIG_PXA_SYSTEMS_CPLDS)	+= pxa_cplds_irqs.o
>
> PXA_SYSTEMS_CPLDS is a bool symbol, so pxa_cplds_irqs.o will never be
> part of a module, correct?
Euh no, this another mistake of mine, it should capable of being a module, to
enable the lubbock/mainstone generic device tree support. I'll fix that for v2
also.

I removed the below comments as the built-in is an error of mine.

Thanks for the review Paul.

Cheers.

-- 
Robert

  reply	other threads:[~2015-04-26 19:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-25 21:13 [PATCH v5 0/3] Fix lubbock and mainstone interrupts Robert Jarzmik
2015-04-25 21:13 ` [PATCH v5 1/3] ARM: pxa: pxa_cplds: add lubbock and mainstone IO Robert Jarzmik
2015-04-26 19:10   ` Paul Bolle
2015-04-26 19:38     ` Robert Jarzmik [this message]
2015-04-25 21:13 ` [PATCH v5 2/3] ARM: pxa: mainstone: use new pxa_cplds driver Robert Jarzmik
2015-04-25 21:13 ` [PATCH v5 3/3] ARM: pxa: lubbock: " Robert Jarzmik
2015-04-25 22:20 ` [PATCH v5 0/3] Fix lubbock and mainstone interrupts Arnd Bergmann
2015-04-26  9:31   ` Robert Jarzmik
2015-04-27  9:16     ` Arnd Bergmann

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=87iocillxd.fsf@belgarion.home \
    --to=robert.jarzmik@free.fr \
    --cc=daniel@zonque.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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