From: Anup Patel <anup@brainfault.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: for-next based on rc4
Date: Wed, 4 Mar 2020 09:22:21 +0530 [thread overview]
Message-ID: <CAAhSdy0LHv63qJ2kmc8DH8+Jgg-JH6Enrpk0kCzncSdaF2TOLg@mail.gmail.com> (raw)
In-Reply-To: <mhng-1817491a-46cd-4ed3-b8cb-bf3319dad665@palmerdabbelt-glaptop1>
Hi Palmer,
On Wed, Mar 4, 2020 at 12:27 AM Palmer Dabbelt <palmer@dabbelt.com> wrote:
>
> rc4 is looking pretty good to me, so I'm going to use that as the starting
> point for the next for-next. A quick poke at my inbox reveals:
>
> * K210 support
> * Static kernel memory permissions
> * Percpu in modules
> * UEFI
> * KGDB
>
> as the big patch sets, but there's some smaller things interspersed that my
> grepping isn't going to catch. For the record, for-next currently contains:
>
> * abc71bf0a703 - (HEAD -> for-next, riscv/for-next) RISC-V: Stop using LOCAL for the uaccess fixups (22 seconds ago) <Palmer Dabbelt>
> * fdff9911f266 - RISC-V: Inline the assembly register save/restore macros (12 minutes ago) <Palmer Dabbelt>
> * 52e7c52d2ded - RISC-V: Stop relying on GCC's register allocator's hueristics (17 minutes ago) <Palmer Dabbelt>
> * 064223b947a8 - RISC-V: Stop putting .sbss in .sdata (17 minutes ago) <Palmer Dabbelt>
> * aff7783392e0 - riscv: force hart_lottery to put in .sdata section (17 minutes ago) <Zong Li>
> * 2fab7a15604c - riscv: Delete CONFIG_SYSFS_SYSCALL from defconfigs (17 minutes ago) <Deepa Dinamani>
> * ab70a73aa45b - riscv: Use flush_icache_mm for flush_icache_user_range (17 minutes ago) <Guo Ren>
>
One important RC fix to address compile issue in Linux-5.6-rcX:
[PATCH] RISC-V: Move all address space definition macros to one place
(Refer, https://lkml.org/lkml/2020/2/24/1084)
Few other candidates for your next branch (based on my manual scan):
1. [PATCH v2 0/4] QEMU Virt Machine Kconfig option
(Refer, https://lore.kernel.org/patchwork/cover/1161456/)
2. [PATCH v10 00/12] Add support for SBI v0.2 and CPU hotplug
(Refer, https://lwn.net/Articles/813394/)
3. [PATCH RESEND v2] riscv: Introduce CONFIG_RELOCATABLE
(Refer, https://patchwork.kernel.org/patch/11417233/)
4. [PATCH] riscv: Use p*d_leaf macros to define p*d_huge
(Refer, https://lkml.org/lkml/2020/2/20/57)
5. [PATCH] riscv: Fix range looking for kernel image memblock
(Refer, https://lkml.org/lkml/2020/2/17/12)
6. [PATCH] riscv: dts: Add GPIO reboot method to HiFive Unleashed DTS file
(Refer, https://www.spinics.net/lists/devicetree/msg335587.html)
7. [PATCH v2 0/3] riscv: mem= support, ioremap exec fix
(Refer, https://lkml.org/lkml/2020/2/15/88)
Regards,
Anup
prev parent reply other threads:[~2020-03-04 3:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 18:57 for-next based on rc4 Palmer Dabbelt
2020-03-04 3:52 ` Anup Patel [this message]
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=CAAhSdy0LHv63qJ2kmc8DH8+Jgg-JH6Enrpk0kCzncSdaF2TOLg@mail.gmail.com \
--to=anup@brainfault.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
/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).