From: Tomasz Torcz <zdzichu@irc.pl>
To: linux-kernel@vger.kernel.org
Cc: mmazur@kernel.pl
Subject: Re: Kernel header policy
Date: Tue, 12 Jul 2005 00:44:14 +0200 [thread overview]
Message-ID: <20050711224414.GB25973@irc.pl> (raw)
In-Reply-To: <Pine.BSO.4.61.0507111533340.23021@login3.srv.ualberta.ca>
On Mon, Jul 11, 2005 at 03:37:47PM -0600, Marc Aurele La France wrote:
> I am contacting you to express my concern over a growing trend in kernel
> development. I am specifically referring to changes being made to kernel
> headers that break compatibility at the userland level, where __KERNEL__
> isn't #define'd.
You should CC person which maintains userspace kernel headers. I've
added Mariusz to CC list.
--
Tomasz Torcz To co nierealne - tutaj jest normalne.
zdzichu@irc.-nie.spam-.pl Ziomale na życie mają tu patenty specjalne.
next prev parent reply other threads:[~2005-07-11 22:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 21:37 Kernel header policy Marc Aurele La France
2005-07-11 21:56 ` Stephen Frost
2005-07-11 22:44 ` Tomasz Torcz [this message]
2005-07-12 2:06 ` Horst von Brand
2005-07-12 13:26 ` Peter Staubach
2005-07-12 13:36 ` Arjan van de Ven
2005-07-12 16:30 ` Alistair John Strachan
2005-07-12 18:38 ` Jim Nance
2005-07-12 19:08 ` Eric Piel
2005-07-12 20:18 ` Tom Rini
2005-07-12 3:07 ` Greg KH
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=20050711224414.GB25973@irc.pl \
--to=zdzichu@irc.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mmazur@kernel.pl \
/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