mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, Jon Masters <jcm@redhat.com>
Subject: Re: [RFC PATCH] kbuild support for %.symtypes files
Date: Mon, 12 Jun 2006 18:32:05 +0200	[thread overview]
Message-ID: <200606121832.05599.agruen@suse.de> (raw)
In-Reply-To: <20060610203348.GB9502@mars.ravnborg.org>

On Saturday, 10 June 2006 22:33, Sam Ravnborg wrote:
> On Tue, May 09, 2006 at 08:37:30PM +0200, Andreas Gruenbacher wrote:
> > Hello,
> >
> > here is a patch that adds a new -T option to genksyms for generating
> > dumps of the type definition that makes up the symbol version hashes.
> > This allows to trace modversion changes back to what caused them. The
> > dump format is the name of the type defined, followed by its definition
> > (which is almost C):
> >
> >   s#list_head struct list_head { s#list_head * next , * prev ; }
>
> Reading something just a little more complex than the above was very
> difficult. So I went on and updated your patch to spit out something
> almost 'C' alike with proper indention and a few newlines too.
>
> The list_head struct looks like this now:
>
> struct#list_head  struct list_head {
> 	struct# list_head * next , * prev;
> };
>
> The real win is for structs with 20+ members, they are now divided up in
> several lines.

Please let's not beautify the output: this would make diffing and grepping 
harder. It's easy to pipe the simple, line oriented format through a 
formatting filter if necessary.

The output could be made more readable by converting the "x#" prefix to C 
keywords (struct, union, etc.). I didn't do this because that would introduce 
parse problems, and constructing dependency graphs from the dump files would 
become tricky.

Andreas

-- 
Andreas Gruenbacher <agruen@suse.de>
Novell / SUSE Labs

  reply	other threads:[~2006-06-12 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 18:37 Andreas Gruenbacher
2006-06-10 20:33 ` Sam Ravnborg
2006-06-12 16:32   ` Andreas Gruenbacher [this message]
2006-06-24 21:54 ` Sam Ravnborg

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=200606121832.05599.agruen@suse.de \
    --to=agruen@suse.de \
    --cc=jcm@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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