All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: sameo@linux.intel.com, lee.jones@linaro.org,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers: mfd: mfd-core: disable irq_domain related code when 'HAVE_GENERIC_HARDIRQS' disabled.
Date: Wed, 24 Jul 2013 13:31:16 +0800	[thread overview]
Message-ID: <51EF66A4.6060704@asianux.com> (raw)
In-Reply-To: <20130724050252.GA4091@osiris>

On 07/24/2013 01:02 PM, Heiko Carstens wrote:
> On Wed, Jul 24, 2013 at 11:33:04AM +0800, Chen Gang wrote:
>> > 'irq_domain' depends on hard irqs, so for the architectures which have
>> > no hard irqs, but still need mfd (e.g. s390), need disable the related
>> > code, or can not pass compiling.
>> > 
>> > The related commit:
>> > 
>> >   "c94bb23 mfd: Make MFD core code Device Tree and IRQ domain aware"
>> > 
>> > The related error: (with allmodconfig under s390)
>> > 
>> >   ERROR: "irq_create_mapping" [drivers/mfd/mfd-core.ko] undefined!
>> > 
>> > 
>> > Signed-off-by: Chen Gang <gang.chen@asianux.com>
> s390 will have GENERIC_HARDIRQS soon (very likely next merge window),
> so lets not add more GENERIC_HARDIRQS ifdefs in the code.
> 

OK, thanks.

-- 
Chen Gang

      reply	other threads:[~2013-07-24  5:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51EE3E20.1090101@asianux.com>
     [not found] ` <20130723104703.GB26775@osiris>
2013-07-23 23:53   ` [PATCH] s390: Kconfig: select 'TTY' when 'S390_GUEST' enabled Chen Gang
2013-07-24  3:33     ` [PATCH] drivers: mfd: mfd-core: disable irq_domain related code when 'HAVE_GENERIC_HARDIRQS' disabled Chen Gang
2013-07-24  5:02       ` Heiko Carstens
2013-07-24  5:31         ` Chen Gang [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=51EF66A4.6060704@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=schwidefsky@de.ibm.com \
    /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.