From: Dan Carpenter <dan.carpenter@oracle.com>
To: Dong Fang <yp.fangdong@gmail.com>
Cc: mfasheh@suse.com, jlbec@evilplan.org, akpm@linux-foundation.org,
jeff.liu@oracle.com, 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
Subject: Re: [PATCH] fs/ocfs2: use list_for_each_entry() instead of list_for_each()
Date: Mon, 29 Jul 2013 10:50:30 +0300 [thread overview]
Message-ID: <20130729075029.GC5053@mwanda> (raw)
In-Reply-To: <1374902815-13349-1-git-send-email-yp.fangdong@gmail.com>
Don't apply this patch. Dong Fang sent a v2 later for some reason.
regards,
dan carpenter
prev parent reply other threads:[~2013-07-29 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 5:26 [PATCH] fs/ocfs2: use list_for_each_entry() instead of list_for_each() Dong Fang
2013-07-29 7:50 ` Dan Carpenter [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=20130729075029.GC5053@mwanda \
--to=dan.carpenter@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jeff.liu@oracle.com \
--cc=jlbec@evilplan.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).