Hi Subrata, Here is the add-on patch which applies on top of the previous patch (as matter of fact, it will apply cleanly without the previous patch too ;)
I have removed the mention of "RHEL 3" from the concerned message. I didn't add any other message like "this should be okay for kernel > xxx", since the new code (original patch) should take care of kernels which are < 2.6.9 and also which are >= 2.6.9 (hence all the kernels). Thus I thought that this message is no longer valid and could be cut short to whats there in this new add-on patch. Yes, I have tested the patch. :) Thanks! Regards, Amit Arora Subrata Modak <[EMAIL PROTECTED]> 01/02/08 03:51 PM Please respond to [EMAIL PROTECTED] To Amit K Arora/India/[EMAIL PROTECTED] cc Anoop V Chakkalakkal/India/[EMAIL PROTECTED], [EMAIL PROTECTED], ltp-list <[email protected]>, Santwana Samantray/India/[EMAIL PROTECTED] Subject Re: [LTP] [PATCH] mlockall02 configuration error and fix On Wed, 2008-01-02 at 15:45 +0530, Amit K Arora wrote: > > Hi Subrata, > > I agree that the message should be changed. But, I think we can do it > as a separate patch. > Will send a separate patch which will apply on top of the current one. That would be really great indeed. --Subrata > Thanks! > > Regards, > Amit Arora > > > Subrata Modak > <[EMAIL PROTECTED]> > > 01/02/08 02:57 PM > Please respond to > [EMAIL PROTECTED] > > > > > To > Amit K > Arora/India/[EMAIL PROTECTED] > cc > [EMAIL PROTECTED], ltp-list <[email protected]>, Santwana Samantray/India/[EMAIL PROTECTED], Anoop V Chakkalakkal/India/[EMAIL PROTECTED] > Subject > Re: [LTP] [PATCH] > mlockall02 > configuration > error and fix > > > > > > > > > On Wed, 2008-01-02 at 09:47 +0100, Carmelo Amoroso wrote: > > Subrata Modak wrote: > > > Hi, > > > > > > Please find below a configuration error reported by Santwana, and, > then > > > the fix for the same by Amit: > > > > > > > ======================================================================================== > > > ---Problem Description--- > > > Configuration error in mlockall02. > > > mlockall02 did not BEHAVE as expected. > > > > > > ---uname output--- > > > Linux 2.6.18-53.el5xen #1 SMP Wed Oct 10 16:48:44 EDT 2007 x86_64 > x86_64 x86_64 GNU/Linux > > > > > > Machine Type = e326m > > > > > > ---Debugger--- > > > A debugger is not configured > > > > > > ---Steps to Reproduce--- > > > 1.Copy and untar ltp testsuite. > > > 2.Issue make followed by make install. > > > 3.Go to testcases/kernel/syscalls/mlockall directory inside the > ltp test suite. > > > 4.Run mlockall02 by issuing ./mlockall02. > > > 5.It produces configuration error as : > > > "mlockall02 1 CONF : mlockall02 did not BEHAVE as > expected.This may be > > > okay if you are running Red Hat Enterprise Linux 3 (RHEL)". > > > > Hello, > > just as a general rule, I don't think it is correct to exit with a > message > > referring to a specific Linux distro. If the issue is in some way > kernel related, > > it should be better something like that > > " ... This may be (or 'is') ok if you run with a kernel version > > x.y.z" > > > > Amit, > > Can this message be removed through a patch and appropriate message > written instead ? > > --Subrata > > > In the embedded world, as mine, this info is certainly more useful. > > > > Regards, > > Carmelo > >
mlockall02_patch2
Description: Binary data
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
