mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Sam Ravnborg <sam@ravnborg.org>, Brian King <brking@us.ibm.com>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Question on MODULE_VERSION macro
Date: Mon, 23 Feb 2004 22:17:18 +0100	[thread overview]
Message-ID: <20040223211718.GA7610@mars.ravnborg.org> (raw)
In-Reply-To: <20040223035321.9C52E2C069@lists.samba.org>

On Mon, Feb 23, 2004 at 02:51:04PM +1100, Rusty Russell wrote:
> In message <20040222232317.GA20083@mars.ravnborg.org> you write:
> > The more correct approach is to list the .o files in the
> > .mod file. Then in sumversion find the corresponding .file.o.cmd, and parse
> > up the name of the corresponding source file (listed as the first filename
> > in the deps_ assignment, and pass this filename to grab_file.
> 
> OK, I've implemented that.  It doesn't complain about non-C files,
> although the parsing might be sub-optimal.
> 
> See get_source_name() for new code.  I also put the explicit depend on
> elfconfig.h in the Makefile.

Took a second look at it.
The reason why you parse the sourcefile, is to locate files included
from the local directory.
But this information is already available in the .module.o.cmd file,
so no reason to parse that information up from the .c file -
and eventually having troubles with .s files.

You can get rid of parse_cpp_line(), include_file(),
and some of the helpers when implementing this algorithm. So all
in all a good simplification.

Note also that in the original implementation you have missed
release_file() in a few places. But when you implement the above
you will hit them.

	Sam

  reply	other threads:[~2004-02-23 20:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040119214233.GF967@beaverton.ibm.com>
2004-01-20  0:57 ` Rusty Russell
2004-01-20  1:17   ` Greg KH
2004-01-20  7:47     ` Rusty Russell
2004-02-20 21:44       ` Brian King
2004-02-21  1:07         ` Rusty Russell
2004-02-22 23:23           ` Sam Ravnborg
2004-02-23  3:51             ` Rusty Russell
2004-02-23 21:17               ` Sam Ravnborg [this message]
2004-02-24  6:13                 ` Rusty Russell
2004-02-25 21:36                   ` Sam Ravnborg
2004-02-26  1:50                     ` Rusty Russell
2004-02-26  7:12                       ` Sam Ravnborg
2004-03-10 20:49     ` Brian King
2004-03-10 21:08       ` 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=20040223211718.GA7610@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@osdl.org \
    --cc=brking@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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

all inboxes | Powered by JetHome®