All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 202989] [MSM-4.14] kernel panic during F2FS GC
Date: Mon, 25 Mar 2019 04:02:16 +0000	[thread overview]
Message-ID: <bug-202989-202145-BbDfZmBBq1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202989-202145@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=202989

--- Comment #9 from yuchao0@huawei.com ---
On 2019/3/25 11:38, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=202989
> 
> --- Comment #8 from Lianjun Huang (hlianjun@gmail.com) ---
> (In reply to Chao Yu from comment #7)
>> I've changed this issue's title to indicate it is from private code repo.
> It is OK.
> 
>>
>> Could you add to Cc below email address of qualcomm's guys, since maybe they
>> can provide some help.
>>
>> stummala@codeaurora.org
>> riteshh@codeaurora.org
> 
> I failed to CC the email addresses above, they seem not to register kernel
> Bugzilla.

Let me Cc them directly. :)

To Sahitya, Ritesh

Do you have time to take a look at this issue?

Thanks,

>

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2019-03-25  4:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 14:39 [Bug 202989] New: kernel panic during F2FS GC bugzilla-daemon
2019-03-22  2:07 ` [Bug 202989] " bugzilla-daemon
2019-03-22  4:08 ` bugzilla-daemon
2019-03-22  9:02 ` bugzilla-daemon
2019-03-22  9:24 ` bugzilla-daemon
2019-03-22  9:26 ` bugzilla-daemon
2019-03-22  9:27 ` bugzilla-daemon
2019-03-23  2:51 ` bugzilla-daemon
2019-03-23  7:38 ` [Bug 202989] [MSM-4.14] " bugzilla-daemon
2019-03-25  3:38 ` bugzilla-daemon
2019-03-25  3:46   ` Chao Yu
2019-03-25 12:56     ` Sahitya Tummala
2019-03-25  4:02 ` bugzilla-daemon [this message]

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=bug-202989-202145-BbDfZmBBq1@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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.