mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Thomas Gleixner <tglx@linutronix.de>, <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] irqchip: Core changes for v4.1 (round 3)
Date: Sat, 11 Apr 2015 11:02:14 +0100	[thread overview]
Message-ID: <0e1460da536654468f9fa0fdd85ed608@www.loen.fr> (raw)
In-Reply-To: <20150410234536.GD18660@io.lakedaemon.net>

Hi Jason,

On 2015-04-11 00:45, Jason Cooper wrote:
> Thomas,
>
> This is the big one.  With this pull request, we remove the legacy 
> hack
> gic_arch_extn, and all users of it.  Replacing it with proper
> representations via stacked domains.  Due to the potentially 
> disruptive
> nature of this series, I've taken several precautions to make sure 
> all
> interested folks are informed and had plenty of chance to object or
> recommend other courses of action.  You're receiving this because 
> there
> have been no objections. ;-)

Note that I have held onto the patch[1] that actually *removes* 
gic-arch_extn
from the GIC code, just in case we need to perform a last minute 
revert.
We can merge that one patch later, once the dust has settled (I don't
expect much noise, but who knows...).

[...]

> A tremendous "Thank you!" to Marc for putting forth all the effort to
> create this series and his gentle 'prodding' to move it along. :)

Well, I'll be thanking you for getting this merged, as well as the 
various
maintainers who have contributed reviews, fixes and improvements to 
this
most disruptive series. This is teamwork! ;-)

Cheers,

         M.

[1]: 
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/315405.html
-- 
Fast, cheap, reliable. Pick two.

  parent reply	other threads:[~2015-04-11 10:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 23:45 Jason Cooper
2015-04-11  9:23 ` Thomas Gleixner
2015-04-11 10:02 ` Marc Zyngier [this message]
2015-04-11 14:32   ` Jason Cooper

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=0e1460da536654468f9fa0fdd85ed608@www.loen.fr \
    --to=marc.zyngier@arm.com \
    --cc=jason@lakedaemon.net \
    --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

all inboxes | Powered by JetHome®