mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arne Caspari <arnem@informatik.uni-bremen.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: bcollins@debian.org, linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: updated: [2.6 patch] ieee1394_core.c: remove unneeded EXPORT_SYMBOL's
Date: Tue, 21 Dec 2004 09:46:15 +0100	[thread overview]
Message-ID: <41C7E2D7.7040806@informatik.uni-bremen.de> (raw)
In-Reply-To: <20041221004237.GJ21288@stusta.de>

Adrian Bunk wrote:
> On Mon, Dec 20, 2004 at 06:51:56PM +0100, Adrian Bunk wrote:
> 
>>...
>>After grepping through your CVS sources, it seems hpsb_read and 
>>hpsb_write are the EXPORT_SYMBOLS affecting you?
>>So keeping them should address your concerns?
>>...

Adrian,

A stable API for the 2.6.x tree would address my concerns :-)

There is one thing missing in the module: It does not allocate 
bandwidth. This will require at least a compare_and_swap function. I 
have not looked into this yet but the required exports for this might be 
the "hpsb_lock" and "hpsb_lock64".

Interesting exports ( by looking through your patch ) would also be
EXPORT_SYMBOL(hpsb_guid_get_entry);
EXPORT_SYMBOL(hpsb_nodeid_get_entry);
Maybe they could be used to make the ConfigROM scan code in the driver 
more generic and cleaner? But if they will be removed, would it be 
better to leave the crappy version with hardcoded offsets in the driver?

I can not answer this question now since I am running low on battery and 
I do not have a power cord with me right now :-(

So to keep the current functionality: Yes, only the _read and _write 
functions are required.

  /Arne

  reply	other threads:[~2004-12-21  8:46 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-20  1:53 Adrian Bunk
2004-12-20  2:10 ` Dan Dennedy
2004-12-20  2:25   ` Adrian Bunk
2004-12-20  2:42     ` Lee Revell
2004-12-20  4:27       ` Dan Dennedy
2004-12-20 22:53         ` Adrian Bunk
2004-12-20 22:58           ` Lee Revell
2004-12-20 23:02             ` Adrian Bunk
2004-12-20 23:21               ` Lee Revell
2004-12-21  0:40               ` Alan Cox
2004-12-21 17:17             ` Greg KH
2004-12-21 17:20               ` Lee Revell
2004-12-21 17:27                 ` Greg KH
2004-12-21 22:19                 ` Theodore Ts'o
2004-12-22 14:08                   ` Alan Cox
2004-12-20  9:01 ` Arne Caspari
2004-12-20 12:15   ` Arjan van de Ven
2004-12-20 13:20     ` Arne Caspari
2004-12-20 14:35       ` Alan Cox
2004-12-22  8:29       ` Arjan van de Ven
2004-12-22  8:57         ` Stefan Richter
2004-12-22 12:01           ` Christoph Hellwig
2004-12-22 12:21             ` Arne Caspari
2004-12-22 16:04             ` Stefan Richter
2004-12-20 14:39   ` Ben Collins
2004-12-20 15:15     ` Alan Cox
2004-12-20 15:46       ` Ben Collins
2004-12-20 20:15         ` Alan Cox
2004-12-21  8:33           ` Arne Caspari
2004-12-21 12:00             ` Adrian Bunk
2004-12-21 12:49               ` Arne Caspari
2004-12-21 17:15                 ` Greg KH
2004-12-21 18:51                   ` Arne Caspari
2004-12-21 18:58                     ` Greg KH
2004-12-20 17:51   ` Adrian Bunk
2004-12-20 21:05     ` Lee Revell
2004-12-20 21:49       ` girish wadhwani
2004-12-21  8:37         ` Arne Caspari
2004-12-21  9:06           ` Bernard Leach
2004-12-21 23:35         ` Pieter Palmers
2004-12-22  0:56           ` Lee Revell
2004-12-21  0:42     ` updated: " Adrian Bunk
2004-12-21  8:46       ` Arne Caspari [this message]
2004-12-21 17:13         ` Greg KH

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=41C7E2D7.7040806@informatik.uni-bremen.de \
    --to=arnem@informatik.uni-bremen.de \
    --cc=bcollins@debian.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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