From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755846AbYIGQAL (ORCPT ); Sun, 7 Sep 2008 12:00:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752926AbYIGP76 (ORCPT ); Sun, 7 Sep 2008 11:59:58 -0400 Received: from xi.wantstofly.org ([83.160.184.112]:41181 "EHLO xi.wantstofly.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752225AbYIGP75 (ORCPT ); Sun, 7 Sep 2008 11:59:57 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=1148133259; d=wantstofly.org; h=date:from:to:cc:subject:message-id:mime-version:content-type: content-disposition:in-reply-to:user-agent; b=mpK5iEXLKDgDTiuqB00v6Cb0IDvdifyWvAUYdOSDNp2yrmidNWekukQONFpKx UqWPnIRn6Gjwct7QCt8OJdquQ== Date: Sun, 7 Sep 2008 17:59:52 +0200 From: Lennert Buytenhek To: "Rafael J. Wysocki" Cc: Linux Kernel Mailing List , Kernel Testers List , Brice Goglin , Lennert Buytenhek , Martin Michlmayr Subject: Re: [Bug #11334] myri10ge: use ioremap_wc: compilation failure on ARM Message-ID: <20080907155952.GA24110@xi.wantstofly.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Sep 06, 2008 at 11:30:38PM +0200, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.26. Please verify if it still should be listed and let me know > (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11334 > Subject : myri10ge: use ioremap_wc: compilation failure on ARM > Submitter : Martin Michlmayr > Date : 2008-08-10 11:25 (28 days old) > References : http://marc.info/?l=linux-netdev&m=121836771727632&w=2 > Handled-By : Lennert Buytenhek > Patch : http://bugzilla.kernel.org/show_bug.cgi?id=11334#c13 Still relevant. A patch to fix this has been submitted and should be in the ARM tree, but it has not made its way upstream yet, and the original submitter has not confirmed that it fixes the problem yet.