Linux-RISC-V Archive on lore.kernel.org
 help / Atom feed
From: Atish Patra <atish.patra@wdc.com>
To: Palmer Dabbelt <palmer@sifive.com>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>
Subject: Re: RISC-V Patchwork
Date: Tue, 20 Nov 2018 10:23:18 -0800
Message-ID: <7b7de9a4-42f7-59d2-c952-bbc5ec023e56@wdc.com> (raw)
Message-ID: <20181120182318.EktLX7hSAHWf1_QjYPLnagM8ApG6eDNIRA14PcBIYeI@z> (raw)
In-Reply-To: <mhng-f1f11265-f6fe-4284-8dc0-a28ac937fdb4@palmer-si-x1c4>

On 11/20/18 8:21 AM, Palmer Dabbelt wrote:
> 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
> 
Awesome. I think you can change the status of the patch from a dropdown 
box, after you logged in with your patchwork id. The available options 
looks pretty much self explanatory unless there is a hidden meaning to 
it ;) ;). As a contributor, we can take a look at the patchwork to for 
the status of the patch. No need of email replies :).

pwclient was helpful in applying the patches directly in case lkml was 
not cc'd on the patch.

https://patchwork.kernel.org/project/linux-riscv/

There is git-pw also. However, I could not get it to working for 
linux-riscv.


Regards,
Atish

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

  parent reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 16:14 palmer
2018-11-20 16:14 ` Palmer Dabbelt
2018-11-20 18:23 ` atish.patra [this message]
2018-11-20 18:23   ` Atish Patra
2018-11-21 18:02   ` mick
2018-11-21 18:02     ` Nick Kossifidis

Reply instructions:

You may reply publically 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=7b7de9a4-42f7-59d2-c952-bbc5ec023e56@wdc.com \
    --to=atish.patra@wdc.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@sifive.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

Linux-RISC-V Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-riscv/0 linux-riscv/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-riscv linux-riscv/ https://lore.kernel.org/linux-riscv \
		linux-riscv@lists.infradead.org infradead-linux-riscv@archiver.kernel.org
	public-inbox-index linux-riscv


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.infradead.lists.linux-riscv


AGPL code for this site: git clone https://public-inbox.org/ public-inbox