From: Atish Patra <Atish.Patra@wdc.com>
To: "rostedt@goodmis.org" <rostedt@goodmis.org>
Cc: "aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"bugzilla-daemon@bugzilla.kernel.org"
<bugzilla-daemon@bugzilla.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: [Bug 209317] ftrace kernel self test failure on RISC-V on 5.8, regression from 5.4.0
Date: Mon, 28 Sep 2020 17:25:36 +0000 [thread overview]
Message-ID: <67278555f143564677878cc849155393a93c018a.camel@wdc.com> (raw)
In-Reply-To: <20200928111341.7eaa98a8@oasis.local.home>
On Mon, 2020-09-28 at 11:13 -0400, Steven Rostedt wrote:
> On Sat, 26 Sep 2020 22:02:35 +0000
> bugzilla-daemon@bugzilla.kernel.org wrote:
>
> > https://bugzilla.kernel.org/show_bug.cgi?id=209317
> >
> > --- Comment #4 from Colin Ian King (colin.king@canonical.com) ---
> > Issue still in 5.9-rc6
> >
>
> Atish,
>
> As the issues bisects down to your commit, care to take a look at
> this.
> (And take ownership of this bug)
>
Yes. I am already looking into this. Colin informed me about the bug
over the weekend.
I couldn't change the ownership as I am not part of the editbugs group.
I have sent an email to helpdesk@kernel.org for access.
> -- Steve
--
Regards,
Atish
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2020-09-28 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-209317-8243@https.bugzilla.kernel.org/>
[not found] ` <bug-209317-8243-E6Z0ICootN@https.bugzilla.kernel.org/>
2020-09-28 15:13 ` [Bug 209317] ftrace kernel self test failure on RISC-V on 5.8, regression from 5.4.0 Steven Rostedt
2020-09-28 17:25 ` Atish Patra [this message]
2020-10-03 17:33 ` Atish Patra
2020-10-05 6:08 ` Zong Li
2020-10-05 18:47 ` 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=67278555f143564677878cc849155393a93c018a.camel@wdc.com \
--to=atish.patra@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rostedt@goodmis.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).