RISC-V Patchwork

[Conor Dooley]

On Thu, Oct 13, 2022 at 04:14:39PM -0700, Palmer Dabbelt wrote:
> On Tue, 11 Oct 2022 09:07:45 PDT (-0700), Conor Dooley wrote:
> > Hey,
> > 
> > As one or two people have already noticed, we've resurrected the
> > patchwork for the RISC-V list @
> > https://patchwork.kernel.org/project/linux-riscv/list/
> > 
> > The patchwork bot should let people know when their patches have been
> > applied. Hopefully it'll help people track what the status of their
> > patches are a little better and try to prevent stuff falling through
> > the cracks in Palmer's inbox.
> > 
> > As an FYI, the statuses that are intended to be used are:
> > - New: No action has been taken yet
> > - Under Review: The maintainer is waiting for review comments from others
> > - Changes Requested: Either the maintainer or a reviewer requested
> >   changes in the patch. The patch author is expected to submit a new
> >   version
> > - Superseded: There's a new version of the patch available
> > - Not Applicable: The patch is not intended for the RISC-V tree
> > - Accepted: The patch has been applied
> > - Rejected: The patch has been rejected, with reasons stated in an
> >   email
> > 
> > I reset patchwork and marked all patches as archived so we would have a
> > fresh start. If your patch has been archived & not applied by the end of
> > this merge window, feel free to resend it.
> > 
> > Thanks,
> > Conor.
> > 
> > @Palmer: hopefully I did the scissors thing correctly..
> 
> b4 doesn't like it, but my old scripts just picked up the whole thing as a
> patch.  I tossed the above bits, LMK if something went off the rails.

I just copied the suggested scissors format from the git-mailinfo man
page and pasted that. I didn't know this prior to 5 mins ago, but
`b4 mbox` splits it on the scissors line, into a patch and an email
inside the mbox - but for w/e reason, `git am` (or `b4 shazam`) then
seems to try and apply the email instead of the patch? Or else pasting
the patch into mutt was a terrible idea? Maybe it's worth mentioning to
Konstantin that things get messed up here, I'll do it tomorrow if I
remember.

Unlikely I'll ever really send many more patches with this format so w/e
at the end of the day. 
Thanks,
Conor.

> 
> > 
> > -- >8 --
> > From f886e8a9def4bd3f2fa8a0a4d7e92c94fe72ea72 Mon Sep 17 00:00:00 2001
> > From: Conor Dooley <conor.dooley at microchip.com>
> > Date: Tue, 11 Oct 2022 16:49:53 +0100
> > Subject: [PATCH] MAINTAINERS: add RISC-V's patchwork
> > 
> > The RISC-V patchwork instance on kernel.org has had some necromancy
> > performed on it & will be used going forward. The statuses that are
> > intended to be used are:
> > - New: No action has been taken yet
> > - Under Review: The maintainer is waiting for review comments from others
> > - Changes Requested: Either the maintainer or a reviewer requested
> >   changes in the patch. The patch author is expected to submit a new
> >   version
> > - Superseded: There's a new version of the patch available
> > - Not Applicable: The patch is not intended for the RISC-V tree
> > - Accepted: The patch has been applied
> > - Rejected: The patch has been rejected, with reasons stated in an
> >   email
> > 
> > Signed-off-by: Conor Dooley <conor.dooley at microchip.com>
> > ---
> >  MAINTAINERS | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 8a5012ba6ff9..e2882dc703d8 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -17516,6 +17516,7 @@ M:	Palmer Dabbelt <palmer at dabbelt.com>
> >  M:	Albert Ou <aou at eecs.berkeley.edu>
> >  L:	linux-riscv at lists.infradead.org
> >  S:	Supported
> > +Q:	https://patchwork.kernel.org/project/linux-riscv/list/
> >  P:	Documentation/riscv/patch-acceptance.rst
> >  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git
> >  F:	arch/riscv/
> 
> _______________________________________________
> linux-riscv mailing list
> linux-riscv at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
>