linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Nick Kossifidis <mick@ics.forth.gr>
To: Atish Patra <atish.patra@wdc.com>
Cc: linux-riscv@lists.infradead.org, Palmer Dabbelt <palmer@sifive.com>
Subject: Re: RISC-V Patchwork
Date: Wed, 21 Nov 2018 20:02:32 +0200	[thread overview]
Message-ID: <28ee2265a0558167042f36f03b4f03c7@mailhost.ics.forth.gr> (raw)
Message-ID: <20181121180232.8x0mIa7KytyvhTo4t5DA1iV-41vmxdTj6TVuxvA_mzw@z> (raw)
In-Reply-To: <7b7de9a4-42f7-59d2-c952-bbc5ec023e56@wdc.com>

Στις 2018-11-20 20:23, Atish Patra έγραψε:
> 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

Thank you !

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

  parent reply	other threads:[~2018-11-21 18:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 16:14 RISC-V Patchwork Palmer Dabbelt
2018-11-20 16:14 ` Palmer Dabbelt
2018-11-20 18:23 ` Atish Patra
2018-11-20 18:23   ` Atish Patra
2018-11-21 18:02   ` Nick Kossifidis [this message]
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=28ee2265a0558167042f36f03b4f03c7@mailhost.ics.forth.gr \
    --to=mick@ics.forth.gr \
    --cc=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
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).