From: Jeff Garzik <jgarzik@pobox.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Rob Landley <rob@landley.net>, linux-scsi@vger.kernel.org
Subject: Re: Questions about scsi.c
Date: Tue, 30 Oct 2007 08:34:50 -0400 [thread overview]
Message-ID: <472724EA.3050502@pobox.com> (raw)
In-Reply-To: <20071025134926.4d209584.rdunlap@xenotime.net>
Randy Dunlap wrote:
> On Thu, 25 Oct 2007 16:40:35 -0500 Rob Landley wrote:
>
>> On Thursday 25 October 2007 12:32:41 pm Randy Dunlap wrote:
>>>> Entirely possible I'm doing something wrong:
>>>>
>>>> <sect1 id="scsi_device.h">
>>>> <title>include/scsi/scsi_device.h</title>
>>>> <para>
>>>> </para>
>>>> !Einclude/scsi/scsi_device.h
>>>> </sect1>
>>> !E is for exported symbols and that file has none.
>>> USe !I instead.
>> So how do I handle a case like drivers/ata/libata-core.c which has
>> EXPORT_SYMBOL() calls for functions that live in (and are documented in)
>> other files, such as ata_scsi_ioctl() in drivers/ata/libata-scsi.c?
>
> I don't see ata_scsi_ioctl() documented at all. Are you looking at
> a newer tree than I am? (i'm using 2.6.24-rc1)
>
> Long-term answer is that we prefer EXPORT_SYMBOL() to be used
> just under the function that is being exported. In this case,
> the maintainer may be disagreeing with that. [cc-ed]
>
> Short-term answer is to use !Isource_filename_where_kernel_doc_is
> as though it's not EXPORTed. I think.
Yeah I tended to prefer that all exports be in one place, rather than
scattered around and difficult to evaluate en masse :)
Jeff
next prev parent reply other threads:[~2007-10-30 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 11:06 Questions about scsi.c Rob Landley
2007-10-25 15:40 ` Randy Dunlap
2007-10-25 18:25 ` Rob Landley
2007-10-25 17:32 ` Randy Dunlap
2007-10-25 19:30 ` Rob Landley
2007-10-25 21:40 ` Rob Landley
2007-10-25 20:49 ` Randy Dunlap
2007-10-25 23:13 ` Rob Landley
2007-10-30 12:34 ` Jeff Garzik [this message]
2007-10-30 14:43 ` James Bottomley
2007-10-30 22:23 ` Rob Landley
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=472724EA.3050502@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rob@landley.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.