From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from exprod6og108.obsmtp.com (exprod6og108.obsmtp.com [64.18.1.21]) by ozlabs.org (Postfix) with SMTP id 9665CB7002 for ; Tue, 19 Jun 2012 07:04:19 +1000 (EST) Received: by ggnc4 with SMTP id c4so5062786ggn.17 for ; Mon, 18 Jun 2012 14:04:17 -0700 (PDT) Subject: Re: [PATCH] PPC: PCI: Fix pcibios_io_space_offset() so it works for 32-bit ptr/64-bit rsrcs Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=us-ascii From: Ben Collins In-Reply-To: <1340051997.2372.27.camel@pasglop> Date: Mon, 18 Jun 2012 16:04:14 -0500 Message-Id: <0F5B9B19-CC65-4DF0-92FB-C34767C42E80@servergy.com> References: <4DC27253-67FC-4A55-8C78-7782D9D0CF53@servergy.com> <1338959744.7150.153.camel@pasglop> <1340051997.2372.27.camel@pasglop> To: Benjamin Herrenschmidt Cc: Bjorn Helgaas , Paul Mackerras , linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Jun 18, 2012, at 3:39 PM, Benjamin Herrenschmidt wrote: > On Mon, 2012-06-18 at 09:23 -0600, Bjorn Helgaas wrote: >> Ooh, sorry about that. Who's going to push this fix? I don't see it >> in Linus' tree yet. If you want me to, please forward me the = original >> patch.=20 >=20 > I want to double check something. We are still printing something = wrong > in the kernel log, so it looks like we have some incorrect carry in = some > arithmetic happening somewhere. Can we at least get this patch in to get things working again? It's = still a regression either way. > Cheers, > Ben. >=20 >=20 -- Ben Collins Servergy, Inc. (757) 243-7557 CONFIDENTIALITY NOTICE: This communication contains privileged and/or = confidential information; and should be maintained with the strictest = confidence. It is intended solely for the use of the person or entity in = which it is addressed. If you are not the intended recipient, you are = STRICTLY PROHIBITED from disclosing, copying, distributing or using any = of this information. If you received this communication in error, please = contact the sender immediately and destroy the material in its entirety, = whether electronic or hard copy.