From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Kyle McMartin <kyle@infradead.org>
Cc: urs.thuermann@volkswagen.de, neilb@suse.de, greg@kroah.com,
bfields@fieldses.org, linux-mtd@lists.infradead.org,
Sam Ravnborg <sam@ravnborg.org>,
dbrownell@users.sourceforge.net, x86 maintainers <x86@kernel.org>,
tiwai@suse.de, Ingo Molnar <mingo@elte.hu>,
linux-media@vger.kernel.org, mchehab@infradead.org,
linux-raid@vger.kernel.org, netfilter@vger.kernel.org,
linux-nfs@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
netfilter-devel@vger.kernel.org, oliver.hartkopp@volkswagen.de,
spi-devel-general@lists.sourceforge.net,
Andrew Morton <akpm@linux-foundation.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [GIT PULL -tip] fix 33 make headers_check warnings
Date: Fri, 23 Jan 2009 21:26:07 +0530 [thread overview]
Message-ID: <1232726167.3504.16.camel@localhost.localdomain> (raw)
In-Reply-To: <20090118041800.GB671@bombadil.infradead.org>
On Sat, 2009-01-17 at 23:18 -0500, Kyle McMartin wrote:
> On Sun, Jan 18, 2009 at 09:08:24AM +0530, Jaswinder Singh Rajput wrote:
> > If this file is _ONLY_ for userspace and kernel cannot use it then what
> > is the point of keeping this file in kernel headers.
> >
>
> There is effectively no point, especially when they reference a variable
> that may or may not exist in the userspace code including it... It seems
> entirely mtd-utils dependent.
>
> Dave, will you queue Adrian's patch to nuke it?
What is the status of include/mtd/jffs2-user.h
--
JSR
next prev parent reply other threads:[~2009-01-23 15:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 20:17 [GIT PULL -tip] fix 33 make headers_check warnings Jaswinder Singh Rajput
2009-01-17 21:37 ` David Woodhouse
2009-01-17 22:04 ` Jan Engelhardt
2009-01-17 22:19 ` Sam Ravnborg
2009-01-17 22:23 ` David Woodhouse
2009-01-18 2:46 ` Jaswinder Singh Rajput
2009-01-17 22:26 ` H. Peter Anvin
2009-01-21 0:38 ` Jaswinder Singh Rajput
2009-01-23 15:59 ` Jaswinder Singh Rajput
2009-01-23 16:04 ` Jaswinder Singh Rajput
2009-01-23 16:11 ` Jan Engelhardt
2009-01-23 16:21 ` Sam Ravnborg
2009-01-23 16:31 ` Jaswinder Singh Rajput
2009-01-23 17:09 ` Sam Ravnborg
2009-01-23 17:28 ` Jaswinder Singh Rajput
2009-01-23 21:33 ` H. Peter Anvin
2009-01-23 21:54 ` Jan Engelhardt
2009-01-23 22:01 ` H. Peter Anvin
2009-01-18 3:05 ` Jaswinder Singh Rajput
2009-01-18 3:33 ` Kyle McMartin
2009-01-18 3:38 ` Jaswinder Singh Rajput
2009-01-18 4:18 ` Kyle McMartin
2009-01-23 15:56 ` Jaswinder Singh Rajput [this message]
2009-01-18 9:13 ` Ingo Molnar
2009-01-18 10:10 ` Sam Ravnborg
2009-01-19 0:24 ` Stephen Rothwell
2009-01-19 2:53 ` Jaswinder Singh Rajput
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=1232726167.3504.16.camel@localhost.localdomain \
--to=jaswinder@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=dbrownell@users.sourceforge.net \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=kyle@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=oliver.hartkopp@volkswagen.de \
--cc=sam@ravnborg.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=tiwai@suse.de \
--cc=urs.thuermann@volkswagen.de \
--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