From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Hellwig <hch@lst.de>
Cc: nate.diller@gmail.com, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Timothy Shimmin <tes@sgi.com>,
Michael Halcrow <mhalcrow@us.ibm.com>
Subject: Re: [PATCH] deprecate memclear_highpage_flush deprecation warnings
Date: Tue, 15 May 2007 09:00:32 -0700 [thread overview]
Message-ID: <20070515090032.e6f94d58.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070515122440.GA8765@lst.de>
On Tue, 15 May 2007 14:24:40 +0200 Christoph Hellwig <hch@lst.de> wrote:
> Recent builds get tons of warnings about memclear_highpage_flush
> beeing deprecated. Turns out it's replaced by zero_user_page
> which takes an additional argument.
>
> Now folks, deprecated is for actual functionality going away, there
> is no need to mark the old name deprecated for such a trivial
> paramter change and rename.
Yes, it's rather trivial, but memclear_highpage_flush() *is* going away.
> This stuff should go to Linus in one
> patch that doesn't create utterly useless warnings and keeps around
> stale interfaces.
>
> Here's a patch to kill memclear_highpage_flush and convert the reaming
> user to make the build a littler more silent, it's more than noisy
> enough due to all the useless addition of __deprecated or __must_check
> to widely used functionality and gcc stupid false positives.
Patches have been prepared which convert all in-kernel users. I thought
I'd dtrt and feed them through maintainers, but that takes time. The
laggards are on cc ;)
next prev parent reply other threads:[~2007-05-15 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 12:24 Christoph Hellwig
2007-05-15 16:00 ` Andrew Morton [this message]
2007-05-15 16:15 ` Christoph Hellwig
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=20070515090032.e6f94d58.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--cc=nate.diller@gmail.com \
--cc=tes@sgi.com \
--cc=torvalds@linux-foundation.org \
--cc=trond.myklebust@fys.uio.no \
/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
Powered by JetHome