Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758081Ab3CYPHw (ORCPT ); Mon, 25 Mar 2013 11:07:52 -0400 Received: from mail-oa0-f49.google.com ([209.85.219.49]:42120 "EHLO mail-oa0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757491Ab3CYPHu (ORCPT ); Mon, 25 Mar 2013 11:07:50 -0400 Message-ID: <51506844.3030108@gmail.com> Date: Mon, 25 Mar 2013 10:07:48 -0500 From: Rob Herring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: Paolo Pisati CC: linux-arm-kernel@lists.infradead.org, Russell King , Jason Cooper , Will Deacon , linux-kernel@vger.kernel.org, Rob Herring , Gregory CLEMENT Subject: Re: [PATCH] ARM: l2x0: don't set .set_debug in l310 case References: <1364149654-16163-1-git-send-email-p.pisati@gmail.com> In-Reply-To: <1364149654-16163-1-git-send-email-p.pisati@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1160 Lines: 32 On 03/24/2013 01:27 PM, Paolo Pisati wrote: > From: Paolo Pisati > > commit 74ddcdb ("l2x0: Only set .set_debug on PL310 r3p0 and earlier") > to actually work needs .set_debug to be not set during definition > > Signed-off-by: Paolo Pisati > --- > arch/arm/mm/cache-l2x0.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/arch/arm/mm/cache-l2x0.c b/arch/arm/mm/cache-l2x0.c > index d457653..37f1364 100644 > --- a/arch/arm/mm/cache-l2x0.c > +++ b/arch/arm/mm/cache-l2x0.c > @@ -724,7 +724,6 @@ static const struct l2x0_of_data pl310_data = { > .flush_all = l2x0_flush_all, > .inv_all = l2x0_inv_all, > .disable = l2x0_disable, > - .set_debug = pl310_set_debug, This actually breaks the cases that need set_debug because the memcpy of the function pointers is after the set_debug init. So I'll come up with something else. Rob -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/