From: Bin Meng <bmeng.cn@gmail.com>
To: Atish Patra <atishp@atishpatra.org>
Cc: linux-riscv <linux-riscv@lists.infradead.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
David Abdurachmanov <david.abdurachmanov@gmail.com>
Subject: Re: Patchwork for linux-riscv
Date: Mon, 3 Aug 2020 15:44:39 +0800 [thread overview]
Message-ID: <CAEUhbmVMrtZFg995DdZhmVAL-W6yRW=NShvApm9__JEoC-_hnQ@mail.gmail.com> (raw)
In-Reply-To: <CAOnJCUKygJk9E2c_Ye2s+xkAa-Ah2naK-YD=8wFGud+JYXhirA@mail.gmail.com>
Hi Atish,
On Fri, Jul 17, 2020 at 1:36 AM Atish Patra <atishp@atishpatra.org> wrote:
>
> On Thu, Jul 16, 2020 at 1:49 AM Bin Meng <bmeng.cn@gmail.com> wrote:
> >
> > 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.
> >
>
> Both OpenSBI & linux-riscv had issues because the hosting server crashed.
> Unfortunately, there was no backup as well which led to losing all
> archives in OpenSBI & linux-riscv.
>
> > > 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?
> >
>
> I thought the patchwork server is different from the mailing list
> server as patchwork did not lose the archives.
> At least that's how the OpenSBI patchwork is set up.
>
> I will check the patchwork admins about this.
>
The patchwork is still not updating. Could you please take a look?
Regards,
Bin
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2020-08-03 7:45 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
2020-07-16 17:36 ` Atish Patra
2020-07-16 17:53 ` Andreas Schwab
2020-08-03 7:44 ` Bin Meng [this message]
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='CAEUhbmVMrtZFg995DdZhmVAL-W6yRW=NShvApm9__JEoC-_hnQ@mail.gmail.com' \
--to=bmeng.cn@gmail.com \
--cc=atishp@atishpatra.org \
--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).