[PATCH v3] RISC-V: Enable dead code elimination

Conor Dooley conor at kernel.org
Sun May 21 08:06:54 PDT 2023


On Sun, May 21, 2023 at 10:56:03PM +0800, Zhangjin Wu wrote:
> > On Sun, May 21, 2023 at 08:41:34PM +0800, Zhangjin Wu wrote:
> > > > On Wed, May 17, 2023 at 04:29:36PM +0800, Zhangjin Wu wrote:

> Btw, where can I check the patch status? 10 years ago, when I worked on
> MIPS architecture, I used patchwork to track the status, not sure, which
> web site we are currently using, lore.kernel.org or still
> patchwork.kernel.org? I use lore to read and send patches now.

Yup, still patchwork for status tracking.
https://patchwork.kernel.org/project/linux-riscv/list/

> 
> > To be honest, I am not quite sure why you are sending some of these
> > things as RFC. The VDSO thing looks like something that should be
> > considered/reviewed properly etc, rather than "hey I have this idea,
> > does anyone have suggestions".
> >
> 
> "RFC" added in my recent patchset is really want to get some feedbacks,
> especially, to learn if it is valuable to continue. As you know, the
> VDSO is required by most of the system, so, touch it should be
> carefully, and dead syscall elimination is another "big" change.
> 
> Thanks for your kindly suggestion, I will remove "RFC" if it is not that
> necessary.

Yea, I understand why you're doing it, but if you do & noone replies
there's a good chance that it'll just get skipped for non-RFC patches
when Palmer is merging stuff.

Cheers,
Conor.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-riscv/attachments/20230521/38123816/attachment.sig>


More information about the linux-riscv mailing list