From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 0/2] ARM IRQ Kconfig patches
Date: Wed, 15 Jun 2011 16:02:38 +0300 [thread overview]
Message-ID: <1308142960-20767-1-git-send-email-balbi@ti.com> (raw)
I have lost count how many times I have sent
these patches. Will someone either take them
in or NAK them so I stop sending ??
Felipe Balbi (2):
arm: Kconfig: select correct HAVE_SPARSE_IRQ symbol
arm: Kconfig: allow OMAP to use sparse IRQ numbering
arch/arm/Kconfig | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
--
1.7.6.rc1
next reply other threads:[~2011-06-15 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 13:02 Felipe Balbi [this message]
2011-06-15 13:02 ` [RESEND PATCH 1/2] arm: Kconfig: select correct HAVE_SPARSE_IRQ symbol Felipe Balbi
2011-06-15 13:02 ` [RESEND PATCH 2/2] arm: Kconfig: allow OMAP to use sparse IRQ numbering Felipe Balbi
2011-06-15 15:14 ` [RESEND PATCH 0/2] ARM IRQ Kconfig patches Russell King - ARM Linux
2011-06-15 15:24 ` Felipe Balbi
2011-06-16 9:19 ` Felipe Balbi
2011-06-15 23:48 ` Kevin Hilman
2011-06-16 11:49 ` Sergei Shtylyov
2011-06-16 21:40 ` Russell King - ARM Linux
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=1308142960-20767-1-git-send-email-balbi@ti.com \
--to=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).