linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2][resend] genirq: export patches
Date: Tue, 21 Aug 2012 11:34:30 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1208211133430.2856@ionos> (raw)
In-Reply-To: <87wr0t5amw.wl%kuninori.morimoto.gx@renesas.com>

On Mon, 20 Aug 2012, Kuninori Morimoto wrote:
> 
> Hi all
> 
> > These are "resend" of genirq export patches.
> > 
> > Kuninori Morimoto (2):
> >       genirq: export irq_set_chip_and_handler_name()
> >       genirq: export dummy_irq_chip
> 
> get_maintainer.pl showed me that Thomas is the maintainer
> of ${LINUX}/kernel/irq/,
> but am I wrong ?
> I think there is no response for these patches.
> 
> Who can care these patches ?
> Should I resend again ?

I'll have a look. Was on vacation and travelling. Still fighting with
the mail backlog.

Thanks,

	tglx

  reply	other threads:[~2012-08-21  9:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06  6:14 linux-next: build failure after merge of the gpio-lw tree Stephen Rothwell
2012-07-06  7:01 ` Linus Walleij
2012-07-06  8:55   ` Kuninori Morimoto
2012-07-08 19:14     ` Linus Walleij
2012-07-09  2:04       ` Kuninori Morimoto
2012-07-09  2:05         ` [PATCH 1/2] genirq: export irq_set_chip_and_handler_name() Kuninori Morimoto
2012-07-09  2:06         ` [PATCH 2/2] genirq: export dummy_irq_chip Kuninori Morimoto
2012-07-09 20:34         ` linux-next: build failure after merge of the gpio-lw tree Linus Walleij
2012-07-24  3:56           ` Kuninori Morimoto
2012-07-31  5:38             ` [PATCH 0/2][resend] genirq: export patches Kuninori Morimoto
2012-07-31  5:39               ` [PATCH 1/2][resend] genirq: export irq_set_chip_and_handler_name() Kuninori Morimoto
2012-08-21 16:38                 ` [tip:irq/core] genirq: Export irq_set_chip_and_handler_name() tip-bot for Kuninori Morimoto
2012-07-31  5:39               ` [PATCH 2/2][resend] genirq: export dummy_irq_chip Kuninori Morimoto
2012-08-21 16:39                 ` [tip:irq/core] genirq: Export dummy_irq_chip tip-bot for Kuninori Morimoto
2012-08-21  0:52               ` [PATCH 0/2][resend] genirq: export patches Kuninori Morimoto
2012-08-21  9:34                 ` Thomas Gleixner [this message]
2012-08-22  5:03           ` linux-next: build failure after merge of the gpio-lw tree Kuninori Morimoto
2012-08-23 21:43             ` Linus Walleij
2012-08-27  1:16               ` Kuninori Morimoto

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=alpine.LFD.2.02.1208211133430.2856@ionos \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuninori.morimoto.gx@gmail.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@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 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).