All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nicos@pcsystems.de>
To: Martin Mares <mj@ucw.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]: problem: pc_keyb.h
Date: Wed, 05 Sep 2001 15:47:49 +0200	[thread overview]
Message-ID: <3B962D05.F24DED64@pcsystems.de> (raw)
In-Reply-To: <3B8FE42B.23804609@pcsystems.de> <20010831213050.A3217@albireo.ucw.cz> <3B929F72.28BAF955@pcsystems.de> <20010905104008.I751@ucw.cz>

okay, convinced.
It wasn't possible to use gpm with 2.0 kernels
anymore, if pc_keyb.h was included.
So i copied the relevant parts to our header file

This will appear in gpm-1.19.5.

Nico

Martin Mares wrote:

> Hello!
>
> > Martin, can't you add the line I sent in the last mail ?
> > This would make it possible to include
> > pc_keyb.h into many programs directly.
>
> Please don't do that, user space programs depending on a particular version
> of kernel headers have already created a horrible mess, so outside the cases
> where you need to share a definition of some kernel<->userspace interface,
> kernel headers really shouldn't be used outside the kernel.
>
>                                 Have a nice fortnight
> --
> Martin `MJ' Mares   <mj@ucw.cz>   http://atrey.karlin.mff.cuni.cz/~mj/
> Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
> Don't take life too seriously
> -- you'll never get out of it alive.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/




      reply	other threads:[~2001-09-05 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-31 19:23 [PATCH]: problem: pc_keyb.h Nico Schottelius
2001-08-31 19:30 ` Martin Mares
2001-09-02 21:06   ` Nico Schottelius
2001-09-05  8:40     ` Martin Mares
2001-09-05 13:47       ` Nico Schottelius [this message]

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=3B962D05.F24DED64@pcsystems.de \
    --to=nicos@pcsystems.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.