From: Christoph Hellwig <hch@infradead.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] mm/{mmap,nommu}.c: several unexports
Date: Sun, 6 Mar 2005 22:47:26 +0000 [thread overview]
Message-ID: <20050306224726.GD5827@infradead.org> (raw)
In-Reply-To: <20050306144319.GG5070@stusta.de>
On Sun, Mar 06, 2005 at 03:43:19PM +0100, Adrian Bunk wrote:
> I didn't find any possible modular usage in the kernel.
>
>
These were there because we had core MM dunctionality duplicated in
every security module. They definitly shouldn't be exported.
next prev parent reply other threads:[~2005-03-06 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 14:43 [2.6 patch] mm/{mmap,nommu}.c: several unexports Adrian Bunk
2005-03-06 22:47 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-24 3:09 Adrian Bunk
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=20050306224726.GD5827@infradead.org \
--to=hch@infradead.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
/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