From: Mark Fasheh <mfasheh@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 2/2] ocfs2_iop_set/get_acl() are also called from the VFS so we must take inode lock
Date: Thu, 16 Apr 2015 14:15:55 -0700 [thread overview]
Message-ID: <20150416211554.GM17170@wotan.suse.de> (raw)
In-Reply-To: <553004BD.9020601@oracle.com>
On Thu, Apr 16, 2015 at 11:51:41AM -0700, Tariq Saeed wrote:
> I have no objection to applying your suggestions and re-submitting the
> patch. Mark, what is the protocol for that. Do I need to mention
> that this is a re-sumit?
If you're re-submitting something that hasn't gone upstream yet it's
sufficient to add a 'V2' (or whatever you like) to the subject line. Also, a
change log in those cases is nice.
Thanks,
--Mark
--
Mark Fasheh
next prev parent reply other threads:[~2015-04-16 21:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 21:46 [Ocfs2-devel] [PATCH 1/2] BUG_ON(lockres->l_level != DLM_LOCK_EX && !checkpointed) tripped in ocfs2_ci_checkpointed Tariq Saeed
2015-04-03 21:46 ` [Ocfs2-devel] [PATCH 2/2] ocfs2_iop_set/get_acl() are also called from the VFS so we must take inode lock Tariq Saeed
2015-04-16 8:48 ` Junxiao Bi
2015-04-16 18:51 ` Tariq Saeed
2015-04-16 21:15 ` Mark Fasheh [this message]
2015-04-16 21:23 ` Tariq Saeed
2015-04-16 21:54 ` Mark Fasheh
2015-04-16 8:34 ` [Ocfs2-devel] [PATCH 1/2] BUG_ON(lockres->l_level != DLM_LOCK_EX && !checkpointed) tripped in ocfs2_ci_checkpointed Junxiao Bi
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=20150416211554.GM17170@wotan.suse.de \
--to=mfasheh@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox