public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Ben Collins <bcollins@debian.org>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, scjody@modernduck.com
Subject: Re: [2.6 patch] drivers/ieee1394/: schedule unused EXPORT_SYMBOL's for removal
Date: Sat, 9 Jul 2005 20:55:57 +0200	[thread overview]
Message-ID: <20050709185557.GI28243@stusta.de> (raw)
In-Reply-To: <20050709075035.GA20151@phunnypharm.org>

On Sat, Jul 09, 2005 at 03:50:35AM -0400, Ben Collins wrote:

> Can we, instead of removing these, wrap then in a "Export full API" config
> option? I've already got several reports from external projects that are

This will end in all distributions having this option enabled resulting 
in no change compared to todays status quo.

> using most of these exported symbols, and I'd hate to make it harder on
> them to use our drivers (for internal projects or otherwise).

What are these external projects?

Is they are internal projects, re-adding the EXPORT_SYMBOL's should be 
trivial for them.

If they aren't only internal internal project, why can't they simply be 
merged (making all discussions about removal of the EXPORT_SYMBOL's they 
use obsolete)?

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-07-09 18:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-03 23:24 [2.6 patch] drivers/ieee1394/: schedule unused EXPORT_SYMBOL's for removal (fwd) Adrian Bunk
2005-07-07 14:45 ` Jody McIntyre
2005-07-07 19:30   ` Stefan Richter
2005-07-09  3:07     ` [2.6 patch] drivers/ieee1394/: schedule unused EXPORT_SYMBOL's for removal Adrian Bunk
2005-07-09  7:22       ` Stefan Richter
2005-07-09  7:50         ` Ben Collins
2005-07-09 10:32           ` alternative [PATCH] 1/2) " Stefan Richter
2005-07-09 16:13             ` Ben Collins
2005-07-09 21:10             ` Ben Collins
2005-07-09 10:33           ` alternative [PATCH] 2/2) " Stefan Richter
2005-07-09 18:55           ` Adrian Bunk [this message]
2005-07-09 19:43             ` [2.6 patch] " Stefan Richter
2005-07-09 20:49             ` Ben Collins
  -- strict thread matches above, loose matches on Subject: below --
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 20:32           ` Dan Dennedy
2005-04-27 21:11             ` Stefan Richter
2005-05-12 22:30               ` Adrian Bunk
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=20050709185557.GI28243@stusta.de \
    --to=bunk@stusta.de \
    --cc=bcollins@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=scjody@modernduck.com \
    --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