All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
	"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
	"len.brown@intel.com" <len.brown@intel.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"pavel@ucw.cz" <pavel@ucw.cz>,
	Stephen Warren <swarren@wwwdotorg.org>
Subject: Re: [REPOST PATCH V2] irq: enable all irqs unconditionally in irq_resume
Date: Thu, 5 Dec 2013 16:37:01 +0530	[thread overview]
Message-ID: <52A05E55.3020605@nvidia.com> (raw)
In-Reply-To: <201312051201.59284.heiko@sntech.de>

On Thursday 05 December 2013 04:31 PM, Heiko Stübner wrote:
> Hi Laxman,
>
> Am Donnerstag, 5. Dezember 2013, 11:49:05 schrieb Laxman Dewangan:
>> Can you please review this patch?
>> This patch is pending from long back for review.
> the patch already made it into the appropriate tree, as can be seen by tip-bot
> message and on [0].
>
>
> Heiko
>
> [0] http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?h=irq-urgent-for-linus&id=ac01810c9d2814238f08a227062e66a35a0e1ea2

Seems I lost the applied mail and that's why I assumed that it is not 
reviewed yet. My bad, Sorry for  noise.
I can see the change in linux-next also.

Thanks Thomas/Heiko for review.

Thanks,
Laxman




      reply	other threads:[~2013-12-05 11:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 14:09 [REPOST PATCH V2] irq: enable all irqs unconditionally in irq_resume Laxman Dewangan
2013-11-25 14:09 ` Laxman Dewangan
2013-11-25 21:28 ` [tip:irq/urgent] irq: Enable " tip-bot for Laxman Dewangan
2013-12-05 10:49 ` [REPOST PATCH V2] irq: enable " Laxman Dewangan
2013-12-05 10:49   ` Laxman Dewangan
2013-12-05 11:01   ` Heiko Stübner
2013-12-05 11:07     ` Laxman Dewangan [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=52A05E55.3020605@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=ian.campbell@citrix.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    --cc=swarren@wwwdotorg.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 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.