public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Grzegorz Jaszczyk <jaz@semihalf.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, tglx@linutronix.de,
	gregory.clement@free-electrons.com,
	thomas.petazzoni@free-electrons.com, alior@marvell.com,
	tawfik@marvell.com, mw@semihalf.com
Subject: Re: [PATCH 0/2] Marvell Armada 375/38x MPIC/MSI fixes
Date: Tue, 21 Oct 2014 18:22:35 -0300	[thread overview]
Message-ID: <5446CE9B.1060907@free-electrons.com> (raw)
In-Reply-To: <20141021151415.GU17447@titan.lakedaemon.net>

On 10/21/2014 12:14 PM, Jason Cooper wrote:
[..]
> 
>> Since this is an important fix, maybe you can schedule it for -rc2?
> 
> I have.  For some reason I have yet to delve into, there were no
> linux-next's during the merge window.  As a result, yesterday's -next
> was the first for the two patches in question.  I'd like to get them
> pushed for -rc2, so I'll probably send the PR tomorrow to get one more
> day in -next.
> 

Great, thanks!
-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

      reply	other threads:[~2014-10-21 21:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25 11:17 [PATCH 0/2] Marvell Armada 375/38x MPIC/MSI fixes Grzegorz Jaszczyk
2014-09-25 11:17 ` [PATCH 1/2] irqchip: armada-370-xp: fix MSI interrupt handling Grzegorz Jaszczyk
2014-09-25 11:17 ` [PATCH 2/2] irqchip: armada-370-xp: fix MPIC " Grzegorz Jaszczyk
2014-09-25 21:56 ` [PATCH 0/2] Marvell Armada 375/38x MPIC/MSI fixes Ezequiel Garcia
2014-10-03 13:50 ` Jason Cooper
2014-10-21 14:19   ` Ezequiel Garcia
2014-10-21 15:14     ` Jason Cooper
2014-10-21 21:22       ` Ezequiel Garcia [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=5446CE9B.1060907@free-electrons.com \
    --to=ezequiel.garcia@free-electrons.com \
    --cc=alior@marvell.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=jaz@semihalf.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mw@semihalf.com \
    --cc=tawfik@marvell.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox