From: Andrew Morton <akpm@linux-foundation.org>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [Bugme-new] [Bug 11027] New: random forward time jumps
Date: Thu, 3 Jul 2008 17:59:32 -0700 [thread overview]
Message-ID: <20080703175932.53ec7151.akpm@linux-foundation.org> (raw)
In-Reply-To: <1215132417.7849.2.camel@localhost>
On Fri, 04 Jul 2008 10:46:57 +1000 Michael Ellerman <michael@ellerman.id.au> wrote:
> On Wed, 2008-07-02 at 11:06 -0700, Andrew Morton wrote:
> > On Wed, 2 Jul 2008 10:49:59 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> >
> > > http://bugzilla.kernel.org/show_bug.cgi?id=11027
> >
> > Hopefully someone in ppc land has set a watch on
> > platform_ppc-32@kernel-bugs.osdl.org?
> >
> > If not, please go to http://bugzilla.kernel.org/userprefs.cgi?tab=email
> > and enter platform_ppc-32@kernel-bugs.osdl.org into the "Users to watch:"
> > box.
>
> Is there a 64-bit equivalent? The obvious address didn't work.
Nope, the only account matching .*ppc.* and .*power.* is
platform_ppc-32@kernel-bugs.osdl.org. (I have elevated bugzilla perms
so I can can query the users list) (everyone should have this - it's
handy).
There is a category "Platform Specific/Hardware"/PPC-64. Those go to
anton@samba.org.
There is a category "Platform Specific/Hardware"/PPC-62. Those go to
platform_ppc-32@kernel-bugs.osdl.org.
So setting a watch on both those accounts would suit.
Or you can just ignore it all. I screen all bugzilla reports and will
ensure that suitable people know about them.
next prev parent reply other threads:[~2008-07-04 1:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11027-10286@http.bugzilla.kernel.org/>
2008-07-02 18:06 ` [Bugme-new] [Bug 11027] New: random forward time jumps Andrew Morton
2008-07-04 0:46 ` Michael Ellerman
2008-07-04 0:59 ` Andrew Morton [this message]
2008-07-04 1:50 ` Tony Breeds
2008-07-04 1:54 ` Michael Ellerman
2008-07-04 3:32 ` Grant Likely
2008-07-07 11:12 ` Josh Boyer
2008-07-04 2:02 ` Andrew Morton
2008-08-18 4:24 ` Tony Breeds
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=20080703175932.53ec7151.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.