From: Richard Weinberger <richard@nod.at>
To: zhangjun <openzhangj@gmail.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Christoph Hellwig <hch@lst.de>,
stable@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: Fwd: ubifs: fix page_count in ->ubifs_migrate_page()
Date: Thu, 13 Dec 2018 13:22:48 +0100 [thread overview]
Message-ID: <7521140.D8HW8ZckG7@blindfold> (raw)
In-Reply-To: <c4f70535-63ba-4c4b-9e79-3ec48a406f52@gmail.com>
Am Donnerstag, 13. Dezember 2018, 13:10:19 CET schrieb zhangjun:
> On 2018/12/13 下午4:30, Richard Weinberger wrote:
> > Am Donnerstag, 13. Dezember 2018, 03:59:50 CET schrieb zhangjun:
> >> hello
> >> I test several kernel version from your commit
> >> 4ac1c17b2044a1b4b2fbed74451947e905fc2992,
> >> there is a bug when migrateing,the following fix i test ok and require
> >> your confirmation.
> > Please keep the CC list intact and give us at least some time to review
> > your patch.
> > Also explain what kind of problem you're facing.
> > In other words, is this a theoretical fix or not?
> >
> > Thanks,
> > //richard
>
> This's my first time to patch upstream,thank you very much for your
> suggestion.
> My problem is my driver to call alloc_cma(),it fail.
> But i find that memory and cma maxchunk is enougth.
> So i building environmentto find what the reason is,test and verify my
> guess.
> i think it not just a theoretical fix but i actually tested it.
Why are you sending this mail now for the third time?
Thanks,
//richard
next prev parent reply other threads:[~2018-12-13 12:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 14:13 ubifs: fix page_count in ->ubifs_migrate_page() zhangjun
[not found] ` <257284e1-ae0c-1652-2edf-64cf8e35187c@gmail.com>
2018-12-13 8:30 ` Fwd: " Richard Weinberger
2018-12-13 12:10 ` zhangjun
2018-12-13 12:22 ` Richard Weinberger [this message]
2018-12-13 12:31 ` zhangjun
2018-12-13 14:23 ` Richard Weinberger
2018-12-13 15:14 ` zhangjun
2018-12-13 22:57 ` Dave Chinner
2018-12-14 6:15 ` zhangjun
2018-12-14 9:12 ` Gao Xiang
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=7521140.D8HW8ZckG7@blindfold \
--to=richard@nod.at \
--cc=hch@lst.de \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=openzhangj@gmail.com \
--cc=stable@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 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.