mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: arjan@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] kernel/sys.c: possible cleanups
Date: Mon, 1 May 2006 02:07:22 -0700	[thread overview]
Message-ID: <20060501020722.62bc5050.akpm@osdl.org> (raw)
In-Reply-To: <20060501085939.GV3570@stusta.de>

Adrian Bunk <bunk@stusta.de> wrote:
>
> So the work would expand to:
>  - writing 200 feature-removal-schedule.txt entries
>  - marking 200 functions and variables as __deprecated_for_modules
>
>  And in a few months:
>  - removing 200 feature-removal-schedule.txt entries
>  - removing 200 __deprecated_for_modules markers
>  - removing the 200 unused exports

Don't bother with all that stuff - a modprobe-time warning across a few
kernel releases is sufficient to make any developers who are dependent upon
an export aware of their problem.

Changing the export to EXPORT_UNUSED_SYMBOL() and then later removing the
export is adequate.

  parent reply	other threads:[~2006-05-01  9:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-01  7:11 Adrian Bunk
2006-05-01  7:18 ` Andrew Morton
2006-05-01  7:35   ` Adrian Bunk
2006-05-01  7:38     ` Andrew Morton
2006-05-01  8:13       ` Adrian Bunk
2006-05-01  7:39     ` Arjan van de Ven
2006-05-01  7:49       ` Andrew Morton
2006-05-01  8:00         ` Arjan van de Ven
2006-05-01  8:20           ` Andrew Morton
2006-05-01  8:59         ` Adrian Bunk
2006-05-01  9:06           ` Arjan van de Ven
2006-05-01  9:07           ` Andrew Morton [this message]
2006-05-01  9:24             ` Adrian Bunk
2006-05-16 17:43   ` [2.6 patch] kernel/sys.c: cleanups Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2006-04-20 17:47 [RFC: 2.6 patch] kernel/sys.c: possible cleanups 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=20060501020722.62bc5050.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=arjan@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
Powered by JetHome