From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Munipradeep Beerakam <mpradeep@linux.vnet.ibm.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH]get_mempolicy01: fix for changing failure due to configuration error
Date: Tue, 23 Jun 2009 20:20:42 +0530 [thread overview]
Message-ID: <1245768642.4860.92.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <1245401736.13600.5.camel@munipradeep-laptop>
> >
> >
> As I don't know what are all the error reporting options LTP have, I
> changed it to CONF. We can change it accordingly to need. Can we report
> it as BROKEN, as set_mempolicy is preventing the get_mempolicy test to
> run?
Muni,
Jiriś patch checked in today should fix this:
Subject: [LTP] [PATCH] Define some syscall numbers in the
linux_syscall_numbers.h file, not to get build failures or crappy
results on other architectures which lack them
Regards--
Subrata
>
> Regards
> Muni
>
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-06-23 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 7:14 [LTP] [PATCH]get_mempolicy01: fix for changing failure due to configuration error Munipradeep Beerakam
2009-06-18 17:31 ` Subrata Modak
2009-06-19 8:55 ` Munipradeep Beerakam
2009-06-23 14:50 ` Subrata Modak [this message]
2009-06-23 16:06 ` Jiri Palecek
2009-06-25 9:10 ` Subrata Modak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1245768642.4860.92.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=mpradeep@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox