From: Jeff Liu <jeff.liu@oracle.com>
To: Dong Fang <yp.fangdong@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
mfasheh@suse.com, jlbec@evilplan.org, akpm@linux-foundation.org,
viro@zeniv.linux.org.uk, sunil.mushran@gmail.com,
tim.gardner@canonical.com, xuejiufei@huawei.com,
shencanquan@huawei.com, ocfs2-devel@oss.oracle.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] fs/ocfs2: use list_for_each_entry() instead of list_for_each()
Date: Tue, 30 Jul 2013 13:01:30 +0800 [thread overview]
Message-ID: <51F748AA.4060706@oracle.com> (raw)
In-Reply-To: <51F7E332.5010708@gmail.com>
Hi Dong,
On 07/31/2013 12:00 AM, Dong Fang wrote:
> On 07/29/2013 04:06 AM, Dan Carpenter wrote:
>> Oh. It appears that nothing changed between v1 and v2. Only the CC
>> list.
>>
>> It's probably that the list moderation on ocfs2-devel was confusing
>> for non-native English speakers the patch submitter thought his
>> patch was dropped.
>>
>> Also mailing lists should have a white list so that I don't get the
>> message every single time.
>>
>> regards,
>> dan carpenter
>>
> sorry about that, i just think i shoud send this patch to linux-fsdevel,
> but ./get_maintainer.pl didn't tell me
It's better to send this patch to ocfs2-devel@oss.oracle.com only, as this
is a specific patch for OCFS2.
Also, we tag OCFS2 kernel patch with "ocfs2" in subject line rather than "fs/ocfs2".
Thanks,
-Jeff
next prev parent reply other threads:[~2013-07-30 5:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 13:23 [PATCH v2] fs/ocfs2: use list_for_each_entry() instead of list_for_each() Dong Fang
2013-07-29 7:49 ` Dan Carpenter
2013-07-29 8:06 ` Dan Carpenter
2013-07-30 16:00 ` Dong Fang
2013-07-30 5:01 ` Jeff Liu [this message]
2013-07-30 18:26 ` Dong Fang
2013-07-30 22:42 ` Dong Fang
2013-07-30 10:51 ` Dan Carpenter
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=51F748AA.4060706@oracle.com \
--to=jeff.liu@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=shencanquan@huawei.com \
--cc=sunil.mushran@gmail.com \
--cc=tim.gardner@canonical.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xuejiufei@huawei.com \
--cc=yp.fangdong@gmail.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;
as well as URLs for NNTP newsgroup(s).