From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: vasily isaenko <vasily.isaenko@oracle.com>,
ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] sparc64 syscall definitions' fixes
Date: Thu, 14 Aug 2014 13:34:46 +0200 [thread overview]
Message-ID: <20140814113446.GA24148@rei.suse.de> (raw)
In-Reply-To: <2112239769.7076776.1408015701225.JavaMail.zimbra@redhat.com>
Hi!
> > 1. Changed '__sparc64__' to 'defined(__sparc__) && defined(__arch64__)'
> > 2. Removed non-implemented syscall numbers from sparc64.in (in accordance
> > to linux-stable/arch/sparc/include/uapi/asm/unistd.h)
> > 2. Re-executed regen.sh
> >
> > Signed-off-by: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
> > ---
> > Hi!
> >
> > I forgot to send it with earlier "SPARC fixes" series.
> >
> > I will be more than happy, if it gets reviewed before the forthcoming
> > release.
>
> Appears to match arch/sparc/kernel/systbls_64.S, ACK.
Looks good to me as well. Please push this (as well as oom fixes).
BTW: I'm finished with the tst_acquire_device() conversion, looking at
the patches at the mailing list I want to get in the containers
cleanup and tst_tmpdir fixes before the pre release freeze and
testing. Is there anything else that should be part of the next
release?
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-08-14 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 8:30 [LTP] [PATCH] sparc64 syscall definitions' fixes Stanislav Kholmanskikh
2014-08-14 11:28 ` Jan Stancek
2014-08-14 11:34 ` chrubis [this message]
[not found] ` <1812950696.7079740.1408016386101.JavaMail.zimbra@redhat.com>
2014-08-14 11:47 ` chrubis
2014-08-14 11:50 ` Jan Stancek
2014-08-14 16:01 ` Stanislav Kholmanskikh
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=20140814113446.GA24148@rei.suse.de \
--to=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=vasily.isaenko@oracle.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