linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	jeremy@goop.org, hughd@google.com, ngupta@vflare.org,
	JBeulich@novell.com, Kurt Hackel <kurt.hackel@oracle.com>,
	npiggin@kernel.dk, akpm@linux-foundation.org, riel@redhat.com,
	hannes@cmpxchg.org, matthew@wil.cx,
	Chris Mason <chris.mason@oracle.com>,
	sjenning@linux.vnet.ibm.com, jackdachef@gmail.com,
	cyclonusj@gmail.com
Subject: Re: Subject: [PATCH V7 1/4] mm: frontswap: swap data structure changes
Date: Fri, 26 Aug 2011 10:46:53 -0400	[thread overview]
Message-ID: <20110826144653.GA889@dumpdata.com> (raw)
In-Reply-To: <24f09c1f-3ff8-4677-a1f7-c3494ced04c1@default>

On Fri, Aug 26, 2011 at 07:15:30AM -0700, Dan Magenheimer wrote:
> > From: KAMEZAWA Hiroyuki [mailto:kamezawa.hiroyu@jp.fujitsu.com]
> > Subject: Re: Subject: [PATCH V7 1/4] mm: frontswap: swap data structure changes
> > 
> > > > From: KAMEZAWA Hiroyuki [mailto:kamezawa.hiroyu@jp.fujitsu.com]
> > > > Subject: Re: Subject: [PATCH V7 1/4] mm: frontswap: swap data structure changes
> > >
> > > Hi Kamezawa-san --
> > >
> > > Domo arigato for the review and feedback!
> > >
> > > > Hmm....could you modify mm/swapfile.c and remove 'static' in the same patch ?
> > >
> > > I separated out this header patch because I thought it would
> > > make the key swap data structure changes more visible.  Are you
> > > saying that it is more confusing?
> > 
> > Yes. I know you add a new header file which is not included but..
> > 
> > At reviewing patch, I check whether all required changes are done.
> > In this case, you turned out the function to be externed but you
> > leave the function definition as 'static'. This unbalance confues me.
> > 
> > I always read patches from 1 to END. When I found an incomplete change
> > in patch 1, I remember it and need to find missng part from patch 2->End.
> > This makes my review confused a little.
> > 
> > In another case, when a patch adds a new file, I check Makefile change.
> > Considering dependency, the patch order should be
> > 
> > 	[patch 1] Documentaion/Config
> > 	[patch 2] Makefile + add new file.
> > 
> > But plesse note: This is my thought. Other guys may have other idea.
> 
> I think that is probably a good approach.  I will try to use it
> for future patches.  But since this frontswap patchset is already
> on V7, I hope it is OK if I continue to organize it for V8 the same
> as it has been, as it might be confusing to previous reviewers
> to change the organization now.

Nah, that is what part of the review process is - keep us on our toes.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2011-08-26 14:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23 14:57 Subject: [PATCH V7 1/4] mm: frontswap: swap data structure changes Dan Magenheimer
2011-08-25  5:33 ` KAMEZAWA Hiroyuki
2011-08-25 17:11   ` Dan Magenheimer
2011-08-26  0:02     ` KAMEZAWA Hiroyuki
2011-08-26 14:15       ` Dan Magenheimer
2011-08-26 14:46         ` Konrad Rzeszutek Wilk [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=20110826144653.GA889@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@novell.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=cyclonusj@gmail.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=jackdachef@gmail.com \
    --cc=jeremy@goop.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kurt.hackel@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matthew@wil.cx \
    --cc=ngupta@vflare.org \
    --cc=npiggin@kernel.dk \
    --cc=riel@redhat.com \
    --cc=sjenning@linux.vnet.ibm.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).