mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] headers_check.pl: disallow extern's
Date: Mon, 29 Dec 2008 13:00:02 +0100	[thread overview]
Message-ID: <20081229120002.GB955@uranus.ravnborg.org> (raw)
In-Reply-To: <200812290515.09121.vapier@gentoo.org>

On Mon, Dec 29, 2008 at 05:15:08AM -0500, Mike Frysinger wrote:
> On Saturday 27 December 2008 13:54:15 Sam Ravnborg wrote:
> > > And we need to get these fixed before we apply this patch.
> > > Otherwise we will break every allyesconfig/allmodconfig builds
> >
> > I turned them into warnings for now.
> > And when I was there I fixed the TODO:
> >
> > From 2bbc376f97c4a75fbbb603b34f73db235a8cd2c1 Mon Sep 17 00:00:00 2001
> > From: Sam Ravnborg <sam@ravnborg.org>
> > Date: Sat, 27 Dec 2008 19:52:20 +0100
> > Subject: [PATCH] kbuild: check for leaked CONFIG_ symbols to userspace
> 
> btw, do you maintain these in a git tree somewhere, or you just posting them 
> to lkml ?  the two kbuild trees under your name on kernel.org/git seems to be 
> lacking this change.  i was looking at adding another check: barf if the 
> header uses __[us]{8,16,32,64} types but does not include linux/types.h.

I push regurlary to kbuild-next.git but you hit a window where I had
asked Linus to pull and thus I avoided any updates.

I the meantime I managed to delete the patches I had queued up so
I need to do a bit of digging before I have a fully updated
kbuild-next.git again.

	Sam

  reply	other threads:[~2008-12-29 11:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-27  7:43 Mike Frysinger
2008-12-27 18:43 ` Sam Ravnborg
2008-12-27 18:54   ` Sam Ravnborg
2008-12-27 19:21     ` Mike Frysinger
2008-12-29 10:15     ` Mike Frysinger
2008-12-29 12:00       ` Sam Ravnborg [this message]
2008-12-27 19:23   ` Mike Frysinger
2008-12-31 16:58 ` Arnd Bergmann
2008-12-31 22:32   ` Mike Frysinger
2009-01-02 23:59     ` Arnd Bergmann
2009-01-03  0:05       ` Arjan van de Ven
2009-01-03  0:09         ` Arnd Bergmann
2009-01-03  1:20           ` Mike Frysinger
2009-01-03  1:40             ` Arnd Bergmann
2009-01-03  1:51 ` Nigel Cunningham

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=20081229120002.GB955@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vapier@gentoo.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®