From: David Woodhouse <dwmw2@infradead.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: rmk@arm.linux.org.uk, 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 12:57:13 +0100 [thread overview]
Message-ID: <1116763033.19183.14.camel@localhost.localdomain> (raw)
In-Reply-To: <200505220008.j4M08uE9025378@hera.kernel.org>
On Sat, 2005-05-21 at 17:08 -0700, Linux Kernel Mailing List wrote:
> author David Woodhouse <dwmw2@org.rmk.(none)> Sat, 21 May 2005 15:52:23 +0100
> committer Russell King <rmk+kernel@arm.linux.org.uk> Sat, 21 May 2005 15:52:23 +0100
>
> When we detect that a 16550 was in fact part of a NatSemi SuperIO chip
> with high-speed mode enabled, we switch it to high-speed mode so that
> baud_base becomes 921600. However, we also need to multiply the baud
> divisor by 8 at the same time, in case it's already in use as a console.
>
> Signed-off-by: David Woodhouse
> Acked-by: Tom Rini
> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Linus, please do not apply patches from me which have my personal
information mangled or removed. I object to having my contributions
anonymised in this way, just as I object to the contributions of others
being anonymised. This makes it harder to contact those responsible for
changes which are committed via Russell's trees, and makes a nonsense of
the practice of including Signed-off-by: lines from the contributor.
If Russell thinks that he's bound by the UK's Data Protection Act, then
he presumably thinks that he's also obliged to honour my demand that he
correct my personal information in his 'database'. His nonsensical
amateur interpretation of the law would put him in a Catch-22 situation.
--
dwmw2
next parent reply other threads:[~2005-05-22 11:59 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 ` David Woodhouse [this message]
2005-05-22 12:59 ` When we detect that a 16550 was in fact part of a NatSemi SuperIO chip 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
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=1116763033.19183.14.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