All of lore.kernel.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] RISC-V Fixes for 5.11-rc1 (or rc2, if it's too late)
Date: Wed, 23 Dec 2020 20:24:05 -0800 (PST)	[thread overview]
Message-ID: <mhng-ab52db2e-d084-4a51-b804-ae41d45ca8db@palmerdabbelt-glaptop> (raw)

merged tag 'riscv-for-linus-5.11-mw0'
The following changes since commit e2ae634014d3a8839a99f8897b3f6346a133a33b:

  Merge tag 'riscv-for-linus-5.11-mw0' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux (2020-12-18 10:43:07 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv-for-linus-5.11-rc1

for you to fetch changes up to de043da0b9e71147ca610ed542d34858aadfc61c:

  RISC-V: Fix usage of memblock_enforce_memory_limit (2020-12-21 21:02:14 -0800)

----------------------------------------------------------------
RISC-V Fixes for 5.11-rc1

* A fix that avoids trying to initialize memory regions outside the
  usable range.

---

I know it's an odd time, but I figured it'd be better to just send this out.
There's a few other fixes on the list that I was considering including, but
there's enough discussion that I didn't want to rush those over the holidays.
I don't see any reason to delay this one any longer, though, as it's relevant
to the ongoing QEMU work.

----------------------------------------------------------------
Atish Patra (1):
      RISC-V: Fix usage of memblock_enforce_memory_limit

 arch/riscv/mm/init.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@dabbelt.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] RISC-V Fixes for 5.11-rc1 (or rc2, if it's too late)
Date: Wed, 23 Dec 2020 20:24:05 -0800 (PST)	[thread overview]
Message-ID: <mhng-ab52db2e-d084-4a51-b804-ae41d45ca8db@palmerdabbelt-glaptop> (raw)

merged tag 'riscv-for-linus-5.11-mw0'
The following changes since commit e2ae634014d3a8839a99f8897b3f6346a133a33b:

  Merge tag 'riscv-for-linus-5.11-mw0' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux (2020-12-18 10:43:07 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv-for-linus-5.11-rc1

for you to fetch changes up to de043da0b9e71147ca610ed542d34858aadfc61c:

  RISC-V: Fix usage of memblock_enforce_memory_limit (2020-12-21 21:02:14 -0800)

----------------------------------------------------------------
RISC-V Fixes for 5.11-rc1

* A fix that avoids trying to initialize memory regions outside the
  usable range.

---

I know it's an odd time, but I figured it'd be better to just send this out.
There's a few other fixes on the list that I was considering including, but
there's enough discussion that I didn't want to rush those over the holidays.
I don't see any reason to delay this one any longer, though, as it's relevant
to the ongoing QEMU work.

----------------------------------------------------------------
Atish Patra (1):
      RISC-V: Fix usage of memblock_enforce_memory_limit

 arch/riscv/mm/init.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2020-12-24  4:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24  4:24 Palmer Dabbelt [this message]
2020-12-24  4:24 ` [GIT PULL] RISC-V Fixes for 5.11-rc1 (or rc2, if it's too late) Palmer Dabbelt
2020-12-24 22:15 ` pr-tracker-bot
2020-12-24 22:15   ` 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=mhng-ab52db2e-d084-4a51-b804-ae41d45ca8db@palmerdabbelt-glaptop \
    --to=palmer@dabbelt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.