From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
torvalds@osdl.org
Subject: Re: When we detect that a 16550 was in fact part of a NatSemi SuperIO chip
Date: Sun, 22 May 2005 22:16:54 +0100 [thread overview]
Message-ID: <1116796612.5730.15.camel@localhost.localdomain> (raw)
In-Reply-To: <20050522144123.F12146@flint.arm.linux.org.uk>
> So, regretfully, this leaves me with the only option but to ignore
> David via all forms of communication until the reason for deference
> is resolved - namely the completion of OSDLs investigation.
Would a few people mind growing up ?
Let me make the obvious little point that nobody has it seems bothered
to notice. Dwmw2 asked you to not mangle his headers. Whatever the data
protection legislation covers is open to some debate but he has clearly
giving you permission to include them unmangled. End of debate both in
DP law and by estoppel.
There is also a really simple and trivial way to deal with data
protection questions in this case with complete clarity, without
tantrums and without an army of lawyers - that is to follow the whole
point and goal of such systems.
Take the existing OSDL statement which must be attached to all
submissions by reference or directly and update it to include
"A public record of contributions is kept which includes the name and
email address of each contributor. By contributing to the kernel project
I accept that my email address provided will be part of that public
record."
and the problem goes away.
I think this change is worth making anyway, perceived privacy is an ever
growing issue of importance in our surveillance and database society
worldwide.
Alan
next prev parent reply other threads:[~2005-05-22 21:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200505220008.j4M08uE9025378@hera.kernel.org>
2005-05-22 11:57 ` When we detect that a 16550 was in fact part of a NatSemi SuperIO chip David Woodhouse
2005-05-22 12:59 ` Russell King
2005-05-22 13:23 ` David Woodhouse
2005-05-22 13:41 ` Russell King
2005-05-22 14:14 ` David Woodhouse
2005-05-22 21:16 ` Alan Cox [this message]
2005-05-22 21:50 ` Linus Torvalds
2005-05-22 22:22 ` Alan Cox
2005-05-22 22:40 ` Linus Torvalds
2005-05-22 22:43 ` Alan Cox
2005-05-23 4:09 ` Willy Tarreau
2005-05-23 5:15 ` Dmitry Torokhov
2005-05-23 7:21 ` Willy Tarreau
2005-05-23 14:27 ` Linus Torvalds
2005-05-22 16:59 ` Linus Torvalds
2005-05-22 17:15 ` David Woodhouse
2005-05-22 18:14 ` Arjan van de Ven
2005-05-22 18:44 ` Russell King
2005-05-22 18:51 ` Arjan van de Ven
2005-05-22 19:03 ` Russell King
2005-05-22 20:31 ` Linus Torvalds
2005-05-22 20:55 ` Brian O'Mahoney
2005-05-22 19:58 ` Brian O'Mahoney
2005-05-22 20:31 ` Lee Revell
2005-05-22 20:48 ` Linus Torvalds
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=1116796612.5730.15.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@osdl.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