From: Al Viro <viro@ZenIV.linux.org.uk>
To: Eric Paris <eparis@redhat.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-cachefs@redhat.com, ecryptfs-devel@lists.launchpad.net,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-arch@vger.kernel.org, linux-mm@kvack.org,
netdev@vger.kernel.org, linux-security-module@vger.kernel.org,
rdunlap@xenotime.net, zohar@linux.vnet.ibm.com,
jmorris@namei.org, serue@us.ibm.com, dhowells@redhat.com,
steved@redhat.com, tiwai@suse.de, tyhicks@linux.vnet.ibm.com,
kirkland@canonical.com, akpm@linux-foundation.org,
npiggin@suse.de, wli@holomorphy.com, mel@csn.ul.ie,
shuber2@gmail.com, dsmith@redhat.com, jack@suse.cz,
jmalicki@metacarta.com, hch@lst.de, bfields@fieldses.org,
neilb@suse.de, agruen@suse.de, john@johnmccutchan.com,
rlove@rlove.org, ebiederm@xmission.com,
heiko.carstens@de.ibm.com, penguin-kernel@I-love.SAKURA.ne.jp,
miklos@szeredi.hu, jens.axboe@oracle.com, arnd@arndb.de
Subject: Re: VFS and IMA API patch series please pull
Date: Wed, 9 Dec 2009 22:44:38 +0000 [thread overview]
Message-ID: <20091209224438.GS14381@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1260393952.3344.18.camel@localhost>
On Wed, Dec 09, 2009 at 04:25:52PM -0500, Eric Paris wrote:
> I'm not sure who the best person to pull this would be. VFS maintainer?
> Al? Should I just send straight to Linus? I'm not sure what the best
> path is. All of the individual fs changes have been acked by their
> respective maintainers and the IMA work has been acked by the IMA
> maintainer. The only patches without CLEAR acks and review are the two
> which remove the get_empty_filp() and init_file() calls.
Sigh... I'll merge it with my queue and push to Linus along with the
rest. It conflicts with some of the pending stuff, but seeing that I
hadn't yelled in time, it's my PITA to deal with.
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2009-12-09 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 21:25 VFS and IMA API patch series please pull Eric Paris
2009-12-09 22:38 ` James Morris
2009-12-09 22:44 ` Al Viro [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=20091209224438.GS14381@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=agruen@suse.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bfields@fieldses.org \
--cc=dhowells@redhat.com \
--cc=dsmith@redhat.com \
--cc=ebiederm@xmission.com \
--cc=ecryptfs-devel@lists.launchpad.net \
--cc=eparis@redhat.com \
--cc=hch@lst.de \
--cc=heiko.carstens@de.ibm.com \
--cc=jack@suse.cz \
--cc=jens.axboe@oracle.com \
--cc=jmalicki@metacarta.com \
--cc=jmorris@namei.org \
--cc=john@johnmccutchan.com \
--cc=kirkland@canonical.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=miklos@szeredi.hu \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rdunlap@xenotime.net \
--cc=rlove@rlove.org \
--cc=serue@us.ibm.com \
--cc=shuber2@gmail.com \
--cc=steved@redhat.com \
--cc=tiwai@suse.de \
--cc=tyhicks@linux.vnet.ibm.com \
--cc=wli@holomorphy.com \
--cc=zohar@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).