From: hch@infradead.org (Christoph Hellwig)
To: linux-riscv@lists.infradead.org
Subject: [PATCH 1/2] Move EM_RISCV into elf-em.h
Date: Sat, 27 Oct 2018 00:46:13 -0700 [thread overview]
Message-ID: <20181027074613.GA7868@infradead.org> (raw)
In-Reply-To: <20181024204036.8799-2-palmer@sifive.com>
On Wed, Oct 24, 2018 at 01:40:35PM -0700, Palmer Dabbelt wrote:
> This should never have been inside our arch port to begin with, it's
> just a relic from when we were maintaining out of tree patches.
>
> Signed-off-by: Palmer Dabbelt <palmer@sifive.com>
Looks good, and probably harmless enought that we should pick it up
for this merge window:
Reviewed-by: Christoph Hellwig <hch@lst.de>
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: kstewart@linuxfoundation.org, aou@eecs.berkeley.edu,
wad@chromium.org, paul@paul-moore.com,
Greg KH <gregkh@linuxfoundation.org>,
Wesley Terpstra <wesley@sifive.com>,
david.abdurachmanov@gmail.com, linux-kernel@vger.kernel.org,
eparis@redhat.com, luto@amacapital.net, dhowells@redhat.com,
linux-audit@redhat.com, pombredanne@nexb.com,
linux-riscv@lists.infradead.org, tglx@linutronix.de,
keescook@chromium.org
Subject: Re: [PATCH 1/2] Move EM_RISCV into elf-em.h
Date: Sat, 27 Oct 2018 00:46:13 -0700 [thread overview]
Message-ID: <20181027074613.GA7868@infradead.org> (raw)
Message-ID: <20181027074613.trzpRLel90lNhQBMf-WgYRz9DhXRQez8ndjflnUq17Q@z> (raw)
In-Reply-To: <20181024204036.8799-2-palmer@sifive.com>
On Wed, Oct 24, 2018 at 01:40:35PM -0700, Palmer Dabbelt wrote:
> This should never have been inside our arch port to begin with, it's
> just a relic from when we were maintaining out of tree patches.
>
> Signed-off-by: Palmer Dabbelt <palmer@sifive.com>
Looks good, and probably harmless enought that we should pick it up
for this merge window:
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-10-27 7:46 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 1:20 [PULL RFC] RISC-V Patches for the 4.20 Merge Window, Part 1 Palmer Dabbelt
2018-10-23 1:20 ` Palmer Dabbelt
2018-10-23 8:20 ` David Abdurachmanov
2018-10-23 8:20 ` David Abdurachmanov
2018-10-24 20:40 ` [PATCH 0/2] RISC-V: Add support for SECCOMP Palmer Dabbelt
2018-10-24 20:40 ` Palmer Dabbelt
2018-10-24 20:40 ` [PATCH 1/2] Move EM_RISCV into elf-em.h Palmer Dabbelt
2018-10-24 20:40 ` Palmer Dabbelt
2018-10-24 21:26 ` Kees Cook
2018-10-24 21:26 ` Kees Cook
2018-10-25 3:04 ` Paul Walmsley
2018-10-25 3:04 ` Paul Walmsley
2018-10-27 7:46 ` Christoph Hellwig [this message]
2018-10-27 7:46 ` Christoph Hellwig
2018-10-27 9:10 ` David Abdurachmanov
2018-10-27 9:10 ` David Abdurachmanov
2018-10-24 20:40 ` [PATCH 2/2] RISC-V: Add support for SECCOMP Palmer Dabbelt
2018-10-24 20:40 ` Palmer Dabbelt
2018-10-24 21:42 ` Kees Cook
2018-10-24 21:42 ` Kees Cook
2018-10-24 22:34 ` Kees Cook
2018-10-24 22:34 ` Kees Cook
2018-10-25 21:02 ` Andy Lutomirski
2018-10-25 21:02 ` Andy Lutomirski
2018-10-27 6:07 ` Palmer Dabbelt
2018-10-27 6:07 ` Palmer Dabbelt
2018-10-25 18:31 ` David Abdurachmanov
2018-10-25 18:31 ` David Abdurachmanov
2018-10-25 20:36 ` Paul Moore
2018-10-25 20:36 ` Paul Moore
2018-10-28 11:07 ` David Abdurachmanov
2018-10-28 11:07 ` David Abdurachmanov
2018-10-29 20:27 ` Palmer Dabbelt
2018-10-29 20:27 ` Palmer Dabbelt
2018-11-02 13:32 ` David Abdurachmanov
2018-11-02 13:32 ` David Abdurachmanov
2018-11-02 15:51 ` Kees Cook
2018-11-02 15:51 ` Kees Cook
2018-10-27 6:07 ` Palmer Dabbelt
2018-10-27 6:07 ` Palmer Dabbelt
2018-10-27 7:55 ` Christoph Hellwig
2018-10-27 7:55 ` Christoph Hellwig
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=20181027074613.GA7868@infradead.org \
--to=hch@infradead.org \
--cc=linux-riscv@lists.infradead.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