From: Oleg Nesterov <oleg@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Arnd Bergmann <arnd@arndb.de>,
x86@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-sh@vger.kernel.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 4/5] x86: don't use asm-generic/ptrace.h
Date: Mon, 20 May 2019 18:02:05 +0200 [thread overview]
Message-ID: <20190520160205.GD771@redhat.com> (raw)
In-Reply-To: <20190520060018.25569-5-hch@lst.de>
On 05/20, Christoph Hellwig wrote:
>
> Doing the indirection through macros for the regs accessors just
> makes them harder to read, so implement the helpers directly.
Acked-by: Oleg Nesterov <oleg@redhat.com>
next prev parent reply other threads:[~2019-05-20 16:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 6:00 remove asm-generic/ptrace.h v2 Christoph Hellwig
2019-05-20 6:00 ` [PATCH 1/5] arm64: don't use asm-generic/ptrace.h Christoph Hellwig
2019-05-20 6:00 ` [PATCH 2/5] powerpc: " Christoph Hellwig
2019-05-20 6:00 ` [PATCH 3/5] sh: " Christoph Hellwig
2019-05-20 6:00 ` [PATCH 4/5] x86: " Christoph Hellwig
2019-05-20 16:02 ` Oleg Nesterov [this message]
2019-05-20 6:00 ` [PATCH 5/5] asm-generic: remove ptrace.h Christoph Hellwig
2019-05-20 16:03 ` Oleg Nesterov
2019-06-04 7:02 ` remove asm-generic/ptrace.h v2 Christoph Hellwig
2019-06-14 7:49 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2019-06-24 5:47 remove asm-generic/ptrace.h v3 Christoph Hellwig
2019-06-24 5:47 ` [PATCH 4/5] x86: don't use asm-generic/ptrace.h Christoph Hellwig
2019-06-24 7:22 ` Thomas Gleixner
2019-05-01 17:39 remove asm-generic/ptrace.h Christoph Hellwig
2019-05-01 17:39 ` [PATCH 4/5] x86: don't use asm-generic/ptrace.h Christoph Hellwig
2019-05-01 21:48 ` Ingo Molnar
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=20190520160205.GD771@redhat.com \
--to=oleg@redhat.com \
--cc=arnd@arndb.de \
--cc=hch@lst.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=x86@kernel.org \
/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).