From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932151AbVHHRoa (ORCPT ); Mon, 8 Aug 2005 13:44:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932152AbVHHRoa (ORCPT ); Mon, 8 Aug 2005 13:44:30 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:47079 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S932151AbVHHRo3 (ORCPT ); Mon, 8 Aug 2005 13:44:29 -0400 Subject: Re: Highmemory Problem with RHEL3 .... 2.4.21-5.ELsmp From: Arjan van de Ven To: Fawad Lateef Cc: linux-kernel@vger.kernel.org In-Reply-To: <1e62d13705080810247d9c9549@mail.gmail.com> References: <1e62d137050807205047daf9e0@mail.gmail.com> <1123489056.3245.28.camel@laptopd505.fenrus.org> <1e62d13705080810247d9c9549@mail.gmail.com> Content-Type: text/plain Date: Mon, 08 Aug 2005 19:44:20 +0200 Message-Id: <1123523060.3245.49.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 (2.2.2-5) Content-Transfer-Encoding: 7bit X-Spam-Score: 2.9 (++) X-Spam-Report: SpamAssassin version 3.0.4 on pentafluge.infradead.org summary: Content analysis details: (2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.1 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address [80.57.133.107 listed in dnsbl.sorbs.net] 2.8 RCVD_IN_DSBL RBL: Received via a relay in list.dsbl.org [] X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2005-08-08 at 22:24 +0500, Fawad Lateef wrote: > Dear Arjan, > > On 8/8/05, Arjan van de Ven wrote: > > > > 1) you probably should use RH support for this > > 2) you forgot to attach your sourcecode / URL to that, including the > > full source of your module. > > > > I already mentioned my code and some details in my previous mail on > the list !!!! No you didn't; you didn't post the module only a rough description of what you changed.... the module is the part that uses this stuff (and since it needs core kernel changes, is required to be GPL so I see no problem posting a URL to it)