linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Paul Walmsley <paul.walmsley@sifive.com>
To: torvalds@linux-foundation.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] RISC-V updates for v5.5-rc6
Date: Sun, 12 Jan 2020 10:55:14 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.21.9999.2001121053560.205587@viisi.sifive.com> (raw)

Linus,

The following changes since commit c79f46a282390e0f5b306007bf7b11a46d529538:

  Linux 5.5-rc5 (2020-01-05 14:23:27 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv/for-v5.5-rc6

for you to fetch changes up to dc6fcba72f0435b7884f2e92fd634bb9f78a2c60:

  riscv: Fixup obvious bug for fp-regs reset (2020-01-12 10:12:44 -0800)

----------------------------------------------------------------
RISC-V updates for v5.5-rc6

Two fixes for RISC-V:

- Clear FP registers during boot when FP support is present, rather than
  when they aren't present

- Move the header files associated with the SiFive L2 cache controller
  to drivers/soc (where the code was recently moved)

----------------------------------------------------------------
Guo Ren (1):
      riscv: Fixup obvious bug for fp-regs reset

Yash Shah (1):
      riscv: move sifive_l2_cache.h to include/soc

 arch/riscv/kernel/head.S                                         | 2 +-
 drivers/edac/sifive_edac.c                                       | 2 +-
 drivers/soc/sifive/sifive_l2_cache.c                             | 2 +-
 {arch/riscv/include/asm => include/soc/sifive}/sifive_l2_cache.h | 6 +++---
 4 files changed, 6 insertions(+), 6 deletions(-)
 rename {arch/riscv/include/asm => include/soc/sifive}/sifive_l2_cache.h (72%)

Kernel object size difference:
   text	   data	    bss	    dec	    hex	filename
6896663	2329920	 313920	9540503	 919397	vmlinux.rv64.orig
6896663	2329920	 313920	9540503	 919397	vmlinux.rv64.patched
6656922	1939060	 257576	8853558	 871836	vmlinux.rv32.orig
6656922	1939060	 257576	8853558	 871836	vmlinux.rv32.patched
1171746	 353372	 130024	1655142	 194166	vmlinux.nommu_virt.orig
1171746	 353372	 130024	1655142	 194166	vmlinux.nommu_virt.patched



             reply	other threads:[~2020-01-12 18:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-12 18:55 Paul Walmsley [this message]
2020-01-13  0:55 ` [GIT PULL] RISC-V updates for v5.5-rc6 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.2001121053560.205587@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).