From: Greg KH <greg@kroah.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, ngupta@vflare.org, konrad.wilk@oracle.com,
kurt.hackel@oracle.com, sjenning@linux.vnet.ibm.com,
chris.mason@oracle.com
Subject: Re: [PATCH V2 1/6] drivers/staging/ramster: cluster/messaging foundation
Date: Thu, 22 Dec 2011 09:31:29 -0800 [thread overview]
Message-ID: <20111222173129.GB28856@kroah.com> (raw)
In-Reply-To: <20111222155050.GA21405@ca-server1.us.oracle.com>
On Thu, Dec 22, 2011 at 07:50:50AM -0800, Dan Magenheimer wrote:
> >From 93c00028709a5d423de77a2fc24d32ec10eca443 Mon Sep 17 00:00:00 2001
> From: Dan Magenheimer <dan.magenheimer@oracle.com>
> Date: Wed, 21 Dec 2011 14:01:54 -0700
> Subject: [PATCH V2 1/6] drivers/staging/ramster: cluster/messaging foundation
Why duplicate this in the email body? That forces me to edit the
patches and remove them, please use git send-email...
> Copy cluster subdirectory from ocfs2. These files implement
> the basic cluster discovery, mapping, heartbeat / keepalive, and
> messaging ("o2net") that ramster requires for internode communication.
> Note: there are NO ramster-specific changes yet; this commit
> does NOT pass checkpatch since the copied source files do not.
Why are you copying the files, and not just exporting the symbols you
need/want to use here? Are you going to be able to properly track
keeping this code in sync?
Same goes for your other patch in this series that copies code, why do
that? Are there goals to eventually not have duplicated code? If so,
what are they, and why not mention them?
thanks,
greg k-h
--
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>
next prev parent reply other threads:[~2011-12-22 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 15:50 Dan Magenheimer
2011-12-22 17:31 ` Greg KH [this message]
2011-12-22 22:06 ` Dan Magenheimer
2011-12-22 22:40 ` Greg KH
2011-12-27 20:34 ` Dan Magenheimer
2011-12-27 20:05 ` Valdis.Kletnieks
2011-12-27 20:29 ` Dan Magenheimer
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=20111222173129.GB28856@kroah.com \
--to=greg@kroah.com \
--cc=chris.mason@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=konrad.wilk@oracle.com \
--cc=kurt.hackel@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ngupta@vflare.org \
--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