public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
	Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL -tip] fix 41 'make headers_check' warnings
Date: Mon, 19 Jan 2009 02:20:24 +0100	[thread overview]
Message-ID: <20090119012024.GA4491@uranus.ravnborg.org> (raw)
In-Reply-To: <20090119093959.ef7f2495.sfr@canb.auug.org.au>

On Mon, Jan 19, 2009 at 09:39:59AM +1100, Stephen Rothwell wrote:
> Hi Jaswinder,
> 
> On Sun, 18 Jan 2009 15:40:54 +0530 Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:
> >
> > diff --git a/include/linux/videodev2.h b/include/linux/videodev2.h
> > index 5571dbe..81fa255 100644
> > --- a/include/linux/videodev2.h
> > +++ b/include/linux/videodev2.h
> > @@ -1480,7 +1480,7 @@ struct v4l2_chip_ident_old {
> >  
> >  #if 1
> >  /* Experimental, meant for debugging, testing and internal use.
> > -   Only implemented if CONFIG_VIDEO_ADV_DEBUG is defined.
> > +   Only implemented if VIDEO_ADV_DEBUG is defined.
> >     You must be root to use these ioctls. Never use these in applications! */
> 
> Is there some reason we cannot fix the tool that does the checking for
> this case?

It could be done - but for now I have kept it very simple.
One day I should preprocess the headers or something to cover more
issues.

	Sam

  reply	other threads:[~2009-01-19  1:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 10:10 [GIT PULL -tip] fix 41 'make headers_check' warnings Jaswinder Singh Rajput
2009-01-18 11:02 ` Ingo Molnar
2009-01-18 11:26   ` Jaswinder Singh Rajput
2009-01-18 12:26     ` Ingo Molnar
2009-01-18 12:57   ` Sam Ravnborg
2009-01-18 13:00     ` Sam Ravnborg
2009-01-18 17:29       ` Ingo Molnar
2009-01-21  0:58         ` Jaswinder Singh Rajput
2009-01-21  1:27   ` Jaswinder Singh Rajput
2009-01-21  5:53     ` Size of sector_t in userspace [Was: fix 41 'make headers_check' warnings] Sam Ravnborg
2009-01-21  8:21       ` Jens Axboe
2009-01-21 11:34         ` Sam Ravnborg
2009-01-18 22:39 ` [GIT PULL -tip] fix 41 'make headers_check' warnings Stephen Rothwell
2009-01-19  1:20   ` Sam Ravnborg [this message]
2009-01-18 22:50 ` Stephen Rothwell
2009-01-19  2:30   ` Jaswinder Singh Rajput
2009-01-19  3:53     ` Stephen Rothwell
2009-01-18 23:53 ` Stephen Rothwell
2009-01-19  2:31   ` Jaswinder Singh Rajput
2009-01-19  3:48     ` Stephen Rothwell
2009-01-19  5:16       ` Jaswinder Singh Rajput
2009-01-18 23:59 ` Stephen Rothwell

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=20090119012024.GA4491@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sfr@canb.auug.org.au \
    --cc=x86@kernel.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