linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: David Abdurachmanov <david.abdurachmanov@gmail.com>
Cc: linux-riscv <linux-riscv@lists.infradead.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: Patchwork for linux-riscv
Date: Thu, 16 Jul 2020 16:49:38 +0800	[thread overview]
Message-ID: <CAEUhbmW2UHRFJct=Ftizdb5zgib0ZRCwEot=sT0skrhoJtWLJg@mail.gmail.com> (raw)
In-Reply-To: <CAEn-LTqnsygh40cqMf4Z41FuZh-tOO2bubNv7vqZUgMbWJT+RA@mail.gmail.com>

On Thu, Jul 16, 2020 at 4:33 PM David Abdurachmanov
<david.abdurachmanov@gmail.com> wrote:
>
> On Thu, Jul 16, 2020 at 7:50 AM Bin Meng <bmeng.cn@gmail.com> wrote:
> >
> > Hi,
> >
> > Patchwork for linux-riscv seems to be stalled.
> > https://patchwork.kernel.org/project/linux-riscv/list/
> >
> > Or am I looking at a wrong place?
>
> Yes, it's stopped updating.
>

Thanks for the information.

> There was an issue with the mailing list (and emails were lost) at
> almost the same time.
>

Ah, I see. OpenSBI mailing list encountered the same problem I remember.

> See: http://lists.infradead.org/pipermail/linux-riscv/
>
> This might have caused an issue with patchwork.

So could someone re-configure the patchwork to bring it back online
for linux-riscv?

Regards,
Bin

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

  reply	other threads:[~2020-07-16  8:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16  4:49 Patchwork for linux-riscv Bin Meng
2020-07-16  8:32 ` David Abdurachmanov
2020-07-16  8:49   ` Bin Meng [this message]
2020-07-16 17:36     ` Atish Patra
2020-07-16 17:53       ` Andreas Schwab
2020-08-03  7:44       ` Bin Meng
2020-08-03 17:46         ` Atish Patra

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='CAEUhbmW2UHRFJct=Ftizdb5zgib0ZRCwEot=sT0skrhoJtWLJg@mail.gmail.com' \
    --to=bmeng.cn@gmail.com \
    --cc=david.abdurachmanov@gmail.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@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).