All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-scsi@vger.kernel.org, jgarzik <jgarzik@pobox.com>
Subject: Re: Questions about scsi.c
Date: Thu, 25 Oct 2007 18:13:21 -0500	[thread overview]
Message-ID: <200710251813.21575.rob@landley.net> (raw)
In-Reply-To: <20071025134926.4d209584.rdunlap@xenotime.net>

On Thursday 25 October 2007 3:49:26 pm 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)

No, I mean I was thinking of adding a kerneldoc comment and noticed the 
discrepancy.

As for already checked-in stuff, substitute ata_std_bios_param, 
ata_scsi_slave_config, and ata_scsi_slave_destroy.  Each of those functions 
has a kerneldoc comment in libata-scsi.c, but the export statement for that 
function is in libata-core.c.

> 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]

Moving the EXPORT_SYMBOL()s would be nice.  The documentation tools don't 
preserve context outside of a single file, and I'd like to get full coverage 
documenting exported symbols before worrying much about internal ones...

> Short-term answer is to use !Isource_filename_where_kernel_doc_is
> as though it's not EXPORTed.  I think.

Except if the EXPORTs got moved/fixed it would then hide them from !I without 
generating any kind of warning.

Actually, for the really short term I can go "see the existing libata book in 
this directory" and foist this problem off on Jeff Garzik. :) (Friday 
deadline.)

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

  reply	other threads:[~2007-10-25 22:13 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 [this message]
2007-10-30 12:34           ` Jeff Garzik
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=200710251813.21575.rob@landley.net \
    --to=rob@landley.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rdunlap@xenotime.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.