Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Zhangjin Wu <falcon@tinylab.org>
Cc: bmeng@tinylab.org, guoren@kernel.org, jszhang@kernel.org,
	linux-riscv@lists.infradead.org, npiggin@gmail.com,
	palmer@rivosinc.com, paul.walmsley@sifive.com,
	paulburton@kernel.org, tim.bird@sony.com
Subject: Re: [PATCH v3] RISC-V: Enable dead code elimination
Date: Sun, 21 May 2023 16:06:54 +0100	[thread overview]
Message-ID: <20230521-cone-payroll-5b3ae791c08f@spud> (raw)
In-Reply-To: <20230521145603.64751-1-falcon@tinylab.org>


[-- Attachment #1.1: Type: text/plain, Size: 1416 bytes --]

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.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

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

  reply	other threads:[~2023-05-21 15:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17  8:29 [PATCH v3] RISC-V: Enable dead code elimination Zhangjin Wu
2023-05-17  8:41 ` Zhangjin Wu
2023-05-21  2:23 ` guoren
2023-05-21  4:09 ` Bin Meng
2023-05-21  8:48 ` Jisheng Zhang
2023-05-21  8:51   ` Jisheng Zhang
2023-05-21  9:08     ` Jisheng Zhang
2023-05-21 12:41   ` Zhangjin Wu
2023-05-21 13:32     ` Conor Dooley
2023-05-21 14:56       ` Zhangjin Wu
2023-05-21 15:06         ` Conor Dooley [this message]
2023-06-20 20:13 ` Nick Desaulniers
2023-06-20 20:17   ` Palmer Dabbelt
2023-06-20 20:22     ` Conor Dooley
2023-06-20 20:26     ` Nick Desaulniers
2023-06-20 20:41       ` Palmer Dabbelt

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=20230521-cone-payroll-5b3ae791c08f@spud \
    --to=conor@kernel.org \
    --cc=bmeng@tinylab.org \
    --cc=falcon@tinylab.org \
    --cc=guoren@kernel.org \
    --cc=jszhang@kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=npiggin@gmail.com \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.com \
    --cc=paulburton@kernel.org \
    --cc=tim.bird@sony.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