public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/ieee1394/: remove unneeded EXPORT_SYMBOL's
Date: Fri, 13 May 2005 00:30:35 +0200	[thread overview]
Message-ID: <20050512223035.GF3603@stusta.de> (raw)
In-Reply-To: <4270001F.8020504@s5r6.in-berlin.de>

On Wed, Apr 27, 2005 at 11:11:59PM +0200, Stefan Richter wrote:
> Dan Dennedy wrote on 2005-04-20:
> >There are technical
> >merits for removal of the external symbols that I accept. I also accept
> >that we have no way of maintaining any sort of stable subsystem for
> >external projects we are not aware of or who are not communicating with
> >us about their requirements (it goes beyond just a stable interface).
> ...
> >I vote to remove external symbols not used by the Linux1394.org modules
> >or the module at http://sourceforge.net/projects/video-2-1394/
> 
> Nobody else posted specific requirements so far. So let's clean up the 
> API. How about this:
>  - Determine a date or event at which unused symbols and functions will
>    vanish. ("Unused": Not used by the mainline drivers and video-2-1394
>    or any other project of similar scope of which the linux1394
>    maintainers are informed soon enough.)

OK.

>  - Add an according entry to Documentation/feature-removal-schedule.txt.

OK.

>  - Add warning comments next to obsolete EXPORT_SYMBOLs. Add warning
>    printks to obsolete functions? (If there are any.)

OK.

> Are there proposals for a date? How about end of June?

OK (now it's perhaps beginning of Juli).


Is this OK for everyone?
If yes, I can prepare a patch.


> Stefan Richter

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


  parent reply	other threads:[~2005-05-12 22:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-17 19:57 [2.6 patch] drivers/ieee1394/: remove unneeded EXPORT_SYMBOL's Adrian Bunk
2005-04-19 19:13 ` Jody McIntyre
2005-04-19 19:43   ` Arjan van de Ven
2005-04-19 22:00     ` Stefan Richter
2005-04-20  7:26       ` Arjan van de Ven
2005-04-20 16:31         ` Stefan Richter
2005-04-20 16:35           ` Arjan van de Ven
2005-04-20 17:09             ` Stefan Richter
2005-04-20 19:19               ` Arjan van de Ven
2005-04-20 20:32           ` Dan Dennedy
2005-04-20 20:49             ` Adrian Bunk
2005-04-20 23:43               ` Stefan Richter
2005-04-27 21:11             ` Stefan Richter
2005-04-27 21:38               ` Jesper Juhl
2005-04-27 21:44                 ` Adrian Bunk
2005-05-12 22:29                   ` Adrian Bunk
2005-05-12 22:30               ` Adrian Bunk [this message]
2005-05-12 23:24                 ` Stefan Richter
2005-05-13 14:00                   ` [2.6 patch] drivers/ieee1394/: schedule unused EXPORT_SYMBOL's for removal 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=20050512223035.GF3603@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.de \
    /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