[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMuHMdX5nR03E46u_p5+cDNYLYZzT3+ZwC0t8Wfu540BFbP5aQ@mail.gmail.com>
Date: Mon, 3 Dec 2018 08:36:03 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: "Dmitry V. Levin" <ldv@...linux.org>
Cc: Andy Lutomirski <luto@...nel.org>, lineprinter@...linux.org,
linux-m68k <linux-m68k@...ts.linux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 06/15] m68k: define syscall_get_arch()
Hi Dmitry,
On Mon, Dec 3, 2018 at 1:24 AM Dmitry V. Levin <ldv@...linux.org> wrote:
> On Sun, Dec 02, 2018 at 11:29:10AM +0100, Geert Uytterhoeven wrote:
> > On Tue, Nov 20, 2018 at 1:15 AM Dmitry V. Levin <ldv@...linux.org> wrote:
> > > syscall_get_arch() is required to be implemented on all architectures
> > > in order to extend the generic ptrace API with PTRACE_GET_SYSCALL_INFO
> > > request.
> > >
> > > Signed-off-by: Dmitry V. Levin <ldv@...linux.org>
> >
> > Reviewed-by: Geert Uytterhoeven <geert@...ux-m68k.org>
> >
> > What's your plan w.r.t. the upstreaming strategy?
> > Do you plan to get this series in as a whole, or through individual architecture
> > maintainers?
>
> Given that the last patch in this series adds an argument
> to syscall_get_arch(), my plan is to get this series in
> as a whole along with PTRACE_GET_SYSCALL_INFO series.
Cool, thanks!
Acked-by: Geert Uytterhoeven <geert@...ux-m68k.org>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists