public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	rmk@arm.linux.org.uk
Subject: Re: When we detect that a 16550 was in fact part of a NatSemi SuperIO chip
Date: Sun, 22 May 2005 18:15:20 +0100	[thread overview]
Message-ID: <1116782121.19183.108.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0505220953300.2307@ppc970.osdl.org>

On Sun, 2005-05-22 at 09:59 -0700, Linus Torvalds wrote:
> So for now, it looks like we either have to make sure that rmk is 
> comfortable with not editing sign-off's (working on it, but I can't 
> guarantee anything), or that you're ok with getting the email stripped, 
> _or_ you will end up having to send patches directly to me rather than to 
> rmk (and face the chaos and bumbling that is Linus).

I think I can handle the chaos and bumbling that is Linus. In fact I
sent this one to Andrew to give it a bit of exposure in the -mm tree
first, but since it's a serial patch I also copied it to Russell as a
courtesy. 

Russell has now said that he committed it by accident, and from that I
infer that he's not going to make a habit of it. So that ought to
suffice for now.

The government department responsible for administering the DPA has a
'Data Protection Help-Line' which I have asked to clarify the situation;
it shouldn't be necessary to pay lawyers to do it. But then again, I can
well imagine that they'll simply refer me to the Act itself rather than
giving a coherent answer, so maybe a paid opinion would be useful.

-- 
dwmw2


  reply	other threads:[~2005-05-22 17:17 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
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 [this message]
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=1116782121.19183.108.camel@localhost.localdomain \
    --to=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@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