linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: James Clark <james.clark@arm.com>,
	"linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>, Leo Yan <leo.yan@arm.com>
Subject: Re: Perf Wiki Appears Broken
Date: Sat, 15 Jun 2024 20:40:32 -0700	[thread overview]
Message-ID: <Zm5esBevamPzcrl_@google.com> (raw)
In-Reply-To: <Zmrtr5Mw_V8a01pD@x1>

On Thu, Jun 13, 2024 at 10:01:35AM -0300, Arnaldo Carvalho de Melo wrote:
> On Thu, Jun 13, 2024 at 01:55:08PM +0100, James Clark wrote:
> > On 10/06/2024 10:19, James Clark wrote:
> > > Hi Arnaldo,
> > > 
> > > I'm not sure if you're still the admin of the Perf wiki, but I'm getting
> > > a login error:
> > > 
> > >  Wiki uses cookies to log in users. You have cookies disabled. Please
> > >  enable them and try again.
> > > 
> > > From a quick Google I think this might be a disk space or configuration
> > > issue.
> > > 
> > > I was planning to add a dockerfile for cross compiling an Arm Perf on
> > > x86. I suppose we can also discuss here if anyone thinks that's useful
> > > or the right place for it.
> > > 
> > > Thanks
> > > James
> > > 
> > 
> > I'm able to log in now. If you poked it, thanks!
> 
> Great! Probably was something transient and the admins fixed it.
> 
> I tried poking a friend that was the admin in the past but he told me he
> wasn't doing it anymore.

I'm still having a problem with login. :(

Thanks,
Namhyung


  reply	other threads:[~2024-06-16  3:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10  9:19 Perf Wiki Appears Broken James Clark
2024-06-13 12:55 ` James Clark
2024-06-13 13:01   ` Arnaldo Carvalho de Melo
2024-06-16  3:40     ` Namhyung Kim [this message]
2024-06-21 17:22       ` yskelg

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=Zm5esBevamPzcrl_@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=james.clark@arm.com \
    --cc=leo.yan@arm.com \
    --cc=linux-perf-users@vger.kernel.org \
    /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).