From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755399AbbDKOc6 (ORCPT ); Sat, 11 Apr 2015 10:32:58 -0400 Received: from aso-006-i435.relay.mailchannels.net ([23.91.64.116]:56896 "EHLO relay.mailchannels.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752896AbbDKOc5 (ORCPT ); Sat, 11 Apr 2015 10:32:57 -0400 X-Sender-Id: duocircle|x-authuser|jac299792458 X-Sender-Id: duocircle|x-authuser|jac299792458 X-MC-Relay: Neutral X-MailChannels-SenderId: duocircle|x-authuser|jac299792458 X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1428762773713:1075148412 X-MC-Ingress-Time: 1428762773713 X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 72.84.113.125 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1+kFYj4FBkwuS++dw+jjiZtfzZQD2h2siU= X-DKIM: OpenDKIM Filter v2.6.8 io 2EB7880013 Date: Sat, 11 Apr 2015 14:32:51 +0000 From: Jason Cooper To: Marc Zyngier Cc: Thomas Gleixner , linux-kernel@vger.kernel.org Subject: Re: [GIT PULL] irqchip: Core changes for v4.1 (round 3) Message-ID: <20150411143251.GF18660@io.lakedaemon.net> References: <20150410234536.GD18660@io.lakedaemon.net> <0e1460da536654468f9fa0fdd85ed608@www.loen.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0e1460da536654468f9fa0fdd85ed608@www.loen.fr> User-Agent: Mutt/1.5.21 (2010-09-15) X-AuthUser: jac299792458 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hey Marc, On Sat, Apr 11, 2015 at 11:02:14AM +0100, Marc Zyngier wrote: > On 2015-04-11 00:45, Jason Cooper wrote: > >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...). Ok, please resend (or ping me) once v4.1-rc1 lands and we'll queue it up as a fix for v4.1. thx, Jason.