From: palmer@sifive.com (Palmer Dabbelt)
To: linux-riscv@lists.infradead.org
Subject: RISC-V Patchwork
Date: Tue, 20 Nov 2018 08:14:10 -0800 (PST) [thread overview]
Message-ID: <mhng-f1f11265-f6fe-4284-8dc0-a28ac937fdb4@palmer-si-x1c4> (raw)
Atish tracked down the documentation for creating a patchwork, which now lives
here
https://patchwork.kernel.org/project/linux-riscv/list/
I have no idea how to use it, so we can all learn together :)
WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@sifive.com>
To: linux-riscv@lists.infradead.org
Subject: RISC-V Patchwork
Date: Tue, 20 Nov 2018 08:14:10 -0800 (PST) [thread overview]
Message-ID: <mhng-f1f11265-f6fe-4284-8dc0-a28ac937fdb4@palmer-si-x1c4> (raw)
Message-ID: <20181120161410.yZbbCrFjuPiBWRdVomdHfDtZW0MMjcMH1mEdhs5JuaA@z> (raw)
Atish tracked down the documentation for creating a patchwork, which now lives
here
https://patchwork.kernel.org/project/linux-riscv/list/
I have no idea how to use it, so we can all learn together :)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2018-11-20 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 16:14 Palmer Dabbelt [this message]
2018-11-20 16:14 ` RISC-V Patchwork Palmer Dabbelt
2018-11-20 18:23 ` Atish Patra
2018-11-20 18:23 ` Atish Patra
2018-11-21 18:02 ` Nick Kossifidis
2018-11-21 18:02 ` Nick Kossifidis
2022-10-11 16:07 Conor Dooley
2022-10-13 23:14 ` Palmer Dabbelt
2022-10-13 23:29 ` Conor Dooley
2022-10-14 16:15 ` Palmer Dabbelt
2022-10-14 18:18 ` Conor Dooley
2023-02-10 21:40 ` Konstantin Ryabitsev
2022-10-26 16:52 ` Conor Dooley
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-f1f11265-f6fe-4284-8dc0-a28ac937fdb4@palmer-si-x1c4 \
--to=palmer@sifive.com \
--cc=linux-riscv@lists.infradead.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.