From: Willy Tarreau <w@1wt.eu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Pranith Kumar <bobby.prani@gmail.com>
Subject: [GIT PULL] nolibc header update for 5.2-rc1 (RISCV support)
Date: Wed, 8 May 2019 16:00:27 +0200 [thread overview]
Message-ID: <20190508140027.GA17190@1wt.eu> (raw)
Hi Linus,
The following changes since commit 80f232121b69cc69a31ccb2b38c1665d770b0710:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next (2019-05-07 22:03:58 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/nolibc.git/ tags/nolibc-5.2-rc1
for you to fetch changes up to 582e84f7b7791bf2a2572559c5e29f3d38a7a535:
tool headers nolibc: add RISCV support (2019-05-08 15:48:43 +0200)
----------------------------------------------------------------
nolibc header update for 5.2-rc1 (RISCV support)
This single commit adds support for the RISCV architecture to the
nolibc header file. Currently the file is only used by rcutorture but
Pranith Kumar who contributed it would like to have this work merged.
I only did some trivial tests to verify that it does not break x86,
which I consider sufficient since all the code is cleanly enclosed
inside a single #if/endif block.
----------------------------------------------------------------
Pranith Kumar (1):
tool headers nolibc: add RISCV support
tools/include/nolibc/nolibc.h | 194 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 194 insertions(+)
next reply other threads:[~2019-05-08 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 14:00 Willy Tarreau [this message]
2019-05-08 20:00 ` [GIT PULL] nolibc header update for 5.2-rc1 (RISCV support) pr-tracker-bot
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=20190508140027.GA17190@1wt.eu \
--to=w@1wt.eu \
--cc=bobby.prani@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).