mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: bunk@stusta.de, sam@ravnborg.org
Subject: Re: [PATCH] 'make headers_install' kbuild target.
Date: Sun, 23 Apr 2006 21:47:46 +0100	[thread overview]
Message-ID: <1145825267.16166.229.camel@shinybook.infradead.org> (raw)
In-Reply-To: <1145672241.16166.156.camel@shinybook.infradead.org>

On Sat, 2006-04-22 at 03:17 +0100, David Woodhouse wrote:
> I expect the kbuild folks to reimplement what I've done in the Makefile,
> but it works well enough to get us started. The text file listing the
> header files will probably want to change -- maybe we'll have a file in
> each directory listing the exportable files in that directory, or maybe
> we'll put a marker in the public files which we can grep for. I don't
> care much. 

And lo... within 10 hours a patch landed in my mailbox which did it all
properly. Now we have Kbuild files in each directory under include/
which list $(header-y) files for copying and $(unifdef-y) files which
need unifdef run on them. Thanks Arnd :)

This is in the git tree at
git://git.infradead.org/~dwmw2/headers-2.6.git

I'm going to stick that in a public directory and give group access to
it, and give out accounts to anyone who wants to assist. Although that
probably isn't necessary -- the individual header file cleanups can
probably go upstream directly rather than into this tree.

-- 
dwmw2


  parent reply	other threads:[~2006-04-23 20:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-22  2:17 David Woodhouse
2006-04-22  9:33 ` Adrian Bunk
2006-04-22 12:03   ` David Woodhouse
2006-04-22 12:38     ` Adrian Bunk
2006-04-22 12:48       ` David Woodhouse
2006-04-22 13:20         ` Adrian Bunk
2006-04-22 13:36           ` David Woodhouse
2006-04-22 14:11             ` Adrian Bunk
2006-04-22 14:26               ` David Woodhouse
2006-04-22 14:44                 ` Adrian Bunk
2006-04-22 14:56                   ` David Woodhouse
2006-04-22 15:30           ` David Woodhouse
2006-04-22 21:13             ` Arnd Bergmann
2006-04-23  7:09               ` Arjan van de Ven
2006-04-23 16:51                 ` Arnd Bergmann
2006-04-23 17:00                 ` Joshua Hudson
2006-04-22 14:14     ` Sam Ravnborg
2006-04-22 14:20       ` Adrian Bunk
2006-04-22 14:28         ` Sam Ravnborg
2006-04-22 14:47           ` David Woodhouse
2006-04-22 14:50           ` Adrian Bunk
2006-04-28 18:15             ` Rob Landley
2006-04-28 18:27               ` David Woodhouse
2006-04-28 19:59                 ` Rob Landley
2006-04-22 14:35         ` David Woodhouse
2006-04-23 20:47 ` David Woodhouse [this message]
2006-04-24  0:12 ` David Woodhouse
2006-04-28 18:13 ` Rob Landley
2006-04-28 18:22   ` David Woodhouse

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=1145825267.16166.229.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=bunk@stusta.de \
    --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

all inboxes | Powered by JetHome®