From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Jiri Palecek <jpalecek@web.de>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH]get_mempolicy01: fix for changing failure due to configuration error
Date: Thu, 25 Jun 2009 14:40:13 +0530 [thread overview]
Message-ID: <1245921013.5542.40.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <200906231806.08741.jpalecek@web.de>
On Tue, 2009-06-23 at 18:06 +0200, Jiri Palecek wrote:
> On Tuesday 23 June 2009 16:50:42 Subrata Modak wrote:
> > > >
> > > >
> > > 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
>
Updating/cleaning linux_syscall_numbers.h is a good idea always.
Regards--
Subrata
> Well, yes and no. The patch does handle the situation (sort of), but it still results in a TBROK (which is wrong, I admit). I think this area (ie. syscalls which are or aren't present in some kernels) should be handled more systematically, especially after what I went through uploading the last version of ltp to Debian. I will think of it and produce some example patches after I send other patches I have in the queue.
>
> Regards
> Jiri Palecek
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2009-06-25 9:58 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
2009-06-23 16:06 ` Jiri Palecek
2009-06-25 9:10 ` Subrata Modak [this message]
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=1245921013.5542.40.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=jpalecek@web.de \
--cc=ltp-list@lists.sourceforge.net \
/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