kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: should include/uapi include header files *unused* in kernel space?
Date: Sun, 22 Jan 2017 08:18:55 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1701220814140.23310@localhost.localdomain> (raw)


  was perusing the UAPI content in the kernel source, prepping for a
course i'm teaching tomorrow, and just noticed there is a header file:

  $ find . -name mtd-user.h
  ./include/uapi/mtd/mtd-user.h
  $

which appears to be *entirely* unreferenced in the entire kernel code
base (outside of the Kbuild file that refers to it):

  $ grep -r 'mtd-user.h' *
  include/uapi/mtd/Kbuild:header-y += mtd-user.h
  $

does this make any sense? am i missing something here? i would have
thought that if a header file includes content that is wholly used
exclusively in user space, it would be part of a package like
"mtd-devel", or something like that.

  is this just for convenience to keep all the mtd stuff in the same
place?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

             reply	other threads:[~2017-01-22 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22 13:18 Robert P. J. Day [this message]
2017-02-03 21:53 ` should include/uapi include header files *unused* in kernel space? Jim Davis
2017-02-04 12:07   ` Robert P. J. Day

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=alpine.LFD.2.20.1701220814140.23310@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).