From: Adrian Bunk <bunk@stusta.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Un-deprecate inter_module_*
Date: Thu, 22 Dec 2005 01:25:46 +0100 [thread overview]
Message-ID: <20051222002546.GJ3917@stusta.de> (raw)
In-Reply-To: <1135210470.31433.24.camel@mindpipe>
On Wed, Dec 21, 2005 at 07:14:30PM -0500, Lee Revell wrote:
> Andrew,
>
> I am also sick of looking at "inter_module_foo is deprecated" warnings.
> They have been deprecated for 6-12 months and obviously no one is fixing
> it. I don't have the time or the inclination to fix it so here's a
> patch to un-deprecate inter_module_*.
>...
In recent -mm kernels (and therefore most likely in 2.6.16) you'll see
the warnings only when your kernel contains one of the "guilty" mtd
modules.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2005-12-22 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 0:14 [PATCH] Un-deprecate inter_module_* Lee Revell
2005-12-22 0:25 ` Adrian Bunk [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=20051222002546.GJ3917@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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