From: Benjamin LaHaise <bcrl@kvack.org>
To: Dong Fang <yp.fangdong@gmail.com>
Cc: viro@zeniv.linux.org.uk, miklos@szeredi.hu,
linux-fsdevel@vger.kernel.org, linux-aio@kvack.org,
fuse-devel@lists.sourceforge.net
Subject: Re: [PATCH] fs: use list_for_each_entry() for list traversing
Date: Tue, 30 Jul 2013 09:10:46 -0400 [thread overview]
Message-ID: <20130730131046.GL1281@kvack.org> (raw)
In-Reply-To: <51F861FB.5050906@gmail.com>
On Tue, Jul 30, 2013 at 09:01:47PM -0400, Dong Fang wrote:
> On 07/30/2013 08:53 AM, Benjamin LaHaise wrote:
> >On Tue, Jul 30, 2013 at 07:01:38PM -0400, Dong Fang wrote:
> >>note: the ./checkpatch will report coding style error:
> >>WARNING: Avoid CamelCase: <Node> ...
> >>
> >>because i don't want to change more origin code in this patch
> >>if need be, i will send a separate patch to fix this problem.
> >
> >It would be a lot easier if you broke up this patch into the changes for
> >the individual subsystems' maintainers.
> >
> > -ben
> >
> do you mean the patch series? such as [PATCH 00/xx] and each individual
> patch for a subsystems?
>
> if so, i will send it later. thx
You can drop the aio bits. That code has been removed by some of Kent's
patches.
-ben
--
"Thought is the essence of where you are now."
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
prev parent reply other threads:[~2013-07-30 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 23:01 [PATCH] fs: use list_for_each_entry() for list traversing Dong Fang
2013-07-30 12:53 ` Benjamin LaHaise
2013-07-31 1:01 ` Dong Fang
2013-07-30 13:10 ` Benjamin LaHaise [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=20130730131046.GL1281@kvack.org \
--to=bcrl@kvack.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
--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 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.