From: Paul Walmsley <paul.walmsley@sifive.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: [GIT PULL] RISC-V updates for v5.3-rc3
Date: Sat, 3 Aug 2019 07:22:25 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1908030720490.3783@viisi.sifive.com> (raw)
Linus,
The following changes since commit 609488bc979f99f805f34e9a32c1e3b71179d10b:
Linux 5.3-rc2 (2019-07-28 12:47:02 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv/for-v5.3-rc3
for you to fetch changes up to b7edabfe843805b7ab8a91396b0782042a289308:
riscv: defconfig: align RV64 defconfig to the output of "make savedefconfig" (2019-07-31 12:26:10 -0700)
----------------------------------------------------------------
RISC-V updates for v5.3-rc3
Three minor RISC-V-related changes for v5.3-rc3:
- Add build ID to VDSO builds to avoid a double-free in perf when
libelf isn't used
- Align the RV64 defconfig to the output of "make savedefconfig" so
subsequent defconfig patches don't get out of hand
- Drop a superfluous DT property from the FU540 SoC DT data (since it
must be already set in board data that includes it)
----------------------------------------------------------------
Mao Han (1):
riscv: Fix perf record without libelf support
Paul Walmsley (2):
riscv: dts: fu540-c000: drop "timebase-frequency"
riscv: defconfig: align RV64 defconfig to the output of "make savedefconfig"
arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 1 -
arch/riscv/configs/defconfig | 10 +++++-----
arch/riscv/kernel/vdso/Makefile | 2 +-
3 files changed, 6 insertions(+), 7 deletions(-)
next reply other threads:[~2019-08-03 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 14:22 Paul Walmsley [this message]
2019-08-03 17:45 ` [GIT PULL] RISC-V updates for v5.3-rc3 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=alpine.DEB.2.21.9999.1908030720490.3783@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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).