From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Paul Burton <paul.burton@mips.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 16/27] mips: define syscall_get_error()
Date: Fri, 21 Dec 2018 04:31:49 +0300 [thread overview]
Message-ID: <20181221013149.GA5299@altlinux.org> (raw)
In-Reply-To: <20181213190015.olf6vhuimjl4jixs@pburton-laptop>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
Hi Paul,
On Thu, Dec 13, 2018 at 07:00:16PM +0000, Paul Burton wrote:
> Hi Dmitry,
>
> On Thu, Dec 13, 2018 at 08:23:02PM +0300, Dmitry V. Levin wrote:
> > syscall_get_error() is required to be implemented on all
> > architectures in addition to already implemented syscall_get_nr(),
> > syscall_get_arguments(), syscall_get_return_value(), and
> > syscall_get_arch() functions in order to extend the generic
> > ptrace API with PTRACE_GET_SYSCALL_INFO request.
> >
> > Cc: Paul Burton <paul.burton@mips.com>
> > Cc: Ralf Baechle <ralf@linux-mips.org>
> > Cc: James Hogan <jhogan@kernel.org>
> > Cc: Oleg Nesterov <oleg@redhat.com>
> > Cc: Andy Lutomirski <luto@kernel.org>
> > Cc: Elvira Khabirova <lineprinter@altlinux.org>
> > Cc: Eugene Syromyatnikov <esyr@redhat.com>
> > Cc: linux-mips@vger.kernel.org
> > Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
>
> Acked-by: Paul Burton <paul.burton@mips.com>
As it looks like the whole series is going to be pinged for quite some time yet,
would you mind taking this patch into the mips tree?
Thanks,
--
ldv
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2018-12-21 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181213171833.GA5240@altlinux.org>
2018-12-13 17:23 ` [PATCH v6 16/27] mips: define syscall_get_error() Dmitry V. Levin
2018-12-13 19:00 ` Paul Burton
2018-12-21 1:31 ` Dmitry V. Levin [this message]
2018-12-13 17:24 ` [PATCH v6 24/27] syscall_get_arch: add "struct task_struct *" argument Dmitry V. Levin
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=20181221013149.GA5299@altlinux.org \
--to=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.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;
as well as URLs for NNTP newsgroup(s).