From: Paul Walmsley <paul.walmsley@sifive.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@sifive.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/9] riscv: remove duplicate macros from ptrace.h
Date: Thu, 25 Apr 2019 13:05:28 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1904251304330.17442@viisi.sifive.com> (raw)
In-Reply-To: <20190425195447.GA22587@lst.de>
On Thu, 25 Apr 2019, Christoph Hellwig wrote:
> On Thu, Apr 25, 2019 at 12:13:18PM -0700, Paul Walmsley wrote:
> >
> >
> > On Thu, 11 Apr 2019, Christoph Hellwig wrote:
> >
> > > No need to have two names for the same thing.
> > >
> > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> >
> > This is probably worth cleaning up across the entire tree.
> >
> > asm-{generic,x86,arm64,powerpc}/ptrace.h all define similar GET_IP/SET_IP
> > macros - although it seems that arch/riscv is the only architecture that
> > uses them.
>
> Yes, we had that discussion before. I've started on a series for that,
> but it is unlikely to touch riscv.
OK, if you're planning to post a separate series for that across the tree,
then:
Reviewed-by: Paul Walmsley <paul.walmsley@sifive.com>
for this RISC-V patch.
- Paul
next prev parent reply other threads:[~2019-04-25 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190411115623.5749-1-hch@lst.de>
[not found] ` <20190411115623.5749-8-hch@lst.de>
2019-04-25 19:13 ` [PATCH 7/9] riscv: remove duplicate macros from ptrace.h Paul Walmsley
2019-04-25 19:54 ` Christoph Hellwig
2019-04-25 20:05 ` Paul Walmsley [this message]
[not found] ` <20190411115623.5749-10-hch@lst.de>
2019-04-25 19:57 ` [PATCH 9/9] riscv: call pm_power_off from machine_halt / machine_power_off Paul Walmsley
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=alpine.DEB.2.21.9999.1904251304330.17442@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.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).