mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Include <asm/termbits.h> from <linux/tty_driver.h>.
Date: Fri, 8 Jun 2007 11:42:10 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706081139310.31532@localhost.localdomain> (raw)
In-Reply-To: <20070608164533.1ed24e79@the-village.bc.nu>

On Fri, 8 Jun 2007, Alan Cox wrote:

> > > >Risk - which compile combinations does it actually show up with and
> > > >is it not better to fix the C file in question not grow the
> > > >horribly tangled include deps further
> > >
> > > struct ktermios; /* that's it */
> >
> > um ... what does that mean?  consider this snippet from
> > <linux/tty_driver.h>:
>
> Which compile combination shows the sequence you are reporting ?

sorry, i don't understand the question.  i'm just running "make" on a
simple module i wrote, using the prototypical in-directory makefile to
build out-of-tree.

the first four lines of my module source file are:

#include <linux/module.h>
#include <linux/init.h>
#include <asm/termbits.h>               /* Shouldn't be necessary */
#include <linux/tty_driver.h>           /* For struct tty_driver */

  if i omit the inclusion of the termbits.h header, i get the
aforementioned error.  beyond that, i'm unclear on what you're asking.

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================

  reply	other threads:[~2007-06-08 15:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 13:29 Robert P. J. Day
2007-06-08 15:30 ` Alan Cox
2007-06-08 15:27   ` Jan Engelhardt
2007-06-08 15:34     ` Robert P. J. Day
2007-06-08 15:45       ` Alan Cox
2007-06-08 15:42         ` Robert P. J. Day [this message]
2007-06-08 16:53           ` Jan Engelhardt
2007-06-08 15:29   ` Robert P. J. Day
2007-06-08 15:48     ` Alan Cox
2007-06-08 15:46       ` Robert P. J. Day
2007-06-08 15:57         ` Alan Cox
2007-06-08 16:15           ` Robert P. J. Day
2007-06-08 16:24             ` Alan Cox
2007-06-08 16:27               ` Robert P. J. Day
2007-06-08 16:41                 ` Alan Cox

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=Pine.LNX.4.64.0706081139310.31532@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®