public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Jim Gifford <maillist@jg555.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Header Sanitizing Project
Date: Thu, 6 Apr 2006 13:38:49 +0200	[thread overview]
Message-ID: <20060406113849.GA4714@suse.cz> (raw)
In-Reply-To: <4431DA7D.80907@jg555.com>

On Mon, Apr 03, 2006 at 07:31:25PM -0700, Jim Gifford wrote:
> I've been working on a way to sanitize the headers. I've come up with a 
> process, that works for what I do, and hope to expand it with all the 
> positive feedback I've been getting. The product of this research is at 
> http://ftp.jg555.com/headers/headers2, and has a requirement of unifdef, 
> which is listed in the script itself.
> 
> When I was working on this project, I've noticed a lot of headers are 
> missing minor little things. Example. most if the if_*.h files are 
> missing asm/types.h. linux/input.h has a complete procedure that should 
> be under __KERNEL__. 

I can't find it in any recent git tree. Which one is it?

> Should I submit these as bugs along with the 
> patches? I have no problem submitting them.
> 
> Please advise me on the proper procedure on the findings, I can provide 
> more details, but everything is in my little script for sanitizing the 
> headers.
> 
> Thank you for all your help
> 
> Jim Gifford
> maillist@jg555.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 

-- 
Vojtech Pavlik
Director SuSE Labs

      reply	other threads:[~2006-04-06 11:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04  2:31 Header Sanitizing Project Jim Gifford
2006-04-06 11:38 ` Vojtech Pavlik [this message]

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=20060406113849.GA4714@suse.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maillist@jg555.com \
    /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