From: Greg KH <greg@kroah.com>
To: Michael Halcrow <mhalcrow@us.ibm.com>
Cc: James Morris <jmorris@redhat.com>,
Phillip Hellewell <phillip@hellewell.homeip.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] eCryptfs: eCryptfs kernel module
Date: Thu, 2 Jun 2005 07:51:54 -0700 [thread overview]
Message-ID: <20050602145153.GA12565@kroah.com> (raw)
In-Reply-To: <20050602123219.GB8855@halcrow.us>
On Thu, Jun 02, 2005 at 07:32:19AM -0500, Michael Halcrow wrote:
> What sort of
> logical chunks would you consider to be appropriate? Separate patches
> for each file (inode.c, file.c, super.c, etc.), which represent sets
> of functions for each major VFS object?
Yes.
thanks,
greg k-h
next prev parent reply other threads:[~2005-06-02 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 5:47 [PATCH 1/3] eCryptfs: eCryptfs kernel module Phillip Hellewell
2005-06-02 7:33 ` Greg KH
2005-06-02 7:33 ` James Morris
2005-06-02 12:32 ` Michael Halcrow
2005-06-02 14:51 ` Greg KH [this message]
2005-06-02 12:28 ` Michael Halcrow
2005-06-02 14:52 ` Greg KH
2005-06-02 16:33 ` James Morris
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=20050602145153.GA12565@kroah.com \
--to=greg@kroah.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--cc=phillip@hellewell.homeip.net \
/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