From: Andrew Morton <akpm@linux-foundation.org>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: hch@infradead.org, viro@ftp.linux.org.uk,
randy.dunlap@oracle.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3] 0/4 fs/ioctl.c coding style, function renaming/factoring
Date: Tue, 30 Oct 2007 16:04:42 -0700 [thread overview]
Message-ID: <20071030160442.e51e2b45.akpm@linux-foundation.org> (raw)
In-Reply-To: <11937731993134-git-send-email-ezk@cs.sunysb.edu>
On Tue, 30 Oct 2007 15:39:55 -0400
Erez Zadok <ezk@cs.sunysb.edu> wrote:
> This series of 4 proposed patches (take 3) changes fs/ioctl.c and Unionfs as
> follows.
The problem is of course that you need these in your tree for ongoing
development, but 2.6.25 is months away. They look OK to me so I suggest
that you go ahead and commit them to your git tree and I'll drop them
again. Please resend them for merging in the 2.6.25-rc1 merge window.
unionfs has been hanging around for a long time now and we should work
towards getting it into 2.6.25 or dropped from -mm (sorry). Right now
would be a great time to get this process underway.
I have only a partial memory of what the sticking points were, and I have
basically zero knowledge of what was done to address them. So could you
please, over the next few weeks:
- Send out a description of what the issues were, and how they were addressed
- If issues remain, describe their impact and possible workarounds, all
that stuff.
- If it mostly-survives all that design-level review and consideration
then let's go for it: get all the patches cleaned up and consolidated and
get them emailed out for review no later than 2.6.24-rc5.
Thanks.
next prev parent reply other threads:[~2007-10-30 23:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 19:39 [PATCH v3] 0/4 fs/ioctl.c coding style, function renaming/factoring Erez Zadok
2007-10-30 19:39 ` [PATCH 1/4] VFS: apply coding standards to fs/ioctl.c Erez Zadok
2007-10-30 19:39 ` [PATCH 2/4] VFS: swap do_ioctl and vfs_ioctl names Erez Zadok
2007-10-30 19:39 ` [PATCH 3/4] VFS: factor out three helpers for FIBMAP/FIONBIO/FIOASYNC file ioctls Erez Zadok
2007-10-30 19:39 ` [PATCH 4/4] Unionfs: use vfs_ioctl Erez Zadok
2007-10-30 23:04 ` Andrew Morton [this message]
2007-10-31 17:37 ` [PATCH v3] 0/4 fs/ioctl.c coding style, function renaming/factoring Erez Zadok
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=20071030160442.e51e2b45.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ezk@cs.sunysb.edu \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=viro@ftp.linux.org.uk \
/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).