All of lore.kernel.org
 help / color / mirror / Atom feed
From: Changwei Ge <chge@linux.alibaba.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2 patches reviewing request
Date: Wed, 11 Sep 2019 11:03:38 +0800	[thread overview]
Message-ID: <37591f1e-b060-57f2-defc-07a278d308ed@linux.alibaba.com> (raw)

Hi list,


I have two ocfs2 patches[1] queued in -mm tree for about 5 months.

Does anyone can help review them?

Maybe, @Joseph do you have some time?

Any comments, advise and questions will be welcomed.

Hopefully, we can merge them into mainline during next merge window to 
close the two issues.


Thanks,

Changwei


[1]:

ocfs2: wait for recovering done after direct unlock request

https://urldefense.proofpoint.com/v2/url?u=http-3A__git.cmpxchg.org_cgit.cgi_linux-2Dmmotm.git_commit_-3Fh-3Dv5.3-2Drc6-2Dmmotm-2D2019-2D08-2D27-2D20-2D39-26id-3D2aaebca745e4cc7c49401374ba1d430ec1fbfe29&d=DwICaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=C7gAd4uDxlAvTdc0vmU6X8CMk6L2iDY8-HD0qT6Fo7Y&m=oygHwA9iyu7kfVMsh1RTKlbgy6A9FCW8sum6cdQy5B4&s=34TJQQ9aFTdpVxd4ABm_kdSQ3djpX2m9_7Bhvsj4zWs&e= 

ocfs2: checkpoint appending truncate log transaction before flushing

https://urldefense.proofpoint.com/v2/url?u=http-3A__git.cmpxchg.org_cgit.cgi_linux-2Dmmotm.git_commit_-3Fh-3Dv5.3-2Drc6-2Dmmotm-2D2019-2D08-2D27-2D20-2D39-26id-3Dabd1a359d33331ae21cf880d579215dc793d925c&d=DwICaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=C7gAd4uDxlAvTdc0vmU6X8CMk6L2iDY8-HD0qT6Fo7Y&m=oygHwA9iyu7kfVMsh1RTKlbgy6A9FCW8sum6cdQy5B4&s=oiMtLNADvCqtacwGcmpke1Pg59CochFnTwAx4wHJ9hY&e= 

             reply	other threads:[~2019-09-11  3:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11  3:03 Changwei Ge [this message]
2019-09-12  1:06 ` [Ocfs2-devel] ocfs2 patches reviewing request Joseph Qi
2019-09-15  1:44 ` Joseph Qi
2019-09-16  3:29   ` Changwei Ge

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=37591f1e-b060-57f2-defc-07a278d308ed@linux.alibaba.com \
    --to=chge@linux.alibaba.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /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.