From: nitin.a.kamble@intel.com
To: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, nitin.a.kamble@intel.com
Subject: [PATCH] a Kconfig fix
Date: Thu, 30 Jan 2014 16:50:09 -0800 [thread overview]
Message-ID: <1391129410-54548-1-git-send-email-nitin.a.kamble@intel.com> (raw)
From: Nitin A Kamble <nitin.a.kamble@intel.com>
This is pull request with a fix for Kconfig dependency issue. It fixes
a build failure when the kernel configuration option GENERIC_IRQ_CHIP
is enabled without enabling the IRQ_DOMAIN config option in the kernel
configuration.
Thanks,
Nitin
Nitin A Kamble (1):
irq: fix a Kconfig dependency
kernel/irq/Kconfig | 1 +
1 file changed, 1 insertion(+)
--
1.8.1.4
next reply other threads:[~2014-01-31 0:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 0:50 nitin.a.kamble [this message]
2014-01-31 0:50 ` [PATCH] irq: fix a Kconfig dependency nitin.a.kamble
2014-01-31 10:27 ` David Rientjes
2014-01-31 17:44 ` Kamble, Nitin A
2014-01-31 20:45 ` David Rientjes
2014-02-04 17:31 ` Kamble, Nitin A
2014-02-04 18:55 ` Thomas Gleixner
2014-02-05 9:22 ` [tip:irq/urgent] genirq: Generic irq chip requires IRQ_DOMAIN tip-bot for Nitin A Kamble
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=1391129410-54548-1-git-send-email-nitin.a.kamble@intel.com \
--to=nitin.a.kamble@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).