From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: gouji <gouji.masayuki@jp.fujitsu.com>,
"'LKML'" <linux-kernel@vger.kernel.org>
Subject: Re: About the fixes of /drivers/serial/8250.C in 2.6.17-rc6 for avoiding habbg-up
Date: Mon, 19 Jun 2006 11:31:42 +0100 [thread overview]
Message-ID: <1150713102.2871.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20060619093219.GA26941@flint.arm.linux.org.uk>
Ar Llu, 2006-06-19 am 10:32 +0100, ysgrifennodd Russell King:
> > Yes, there is a bug in this version that was not in the one I submitted,
> > someone added an improvement.
>
> I disagree - in the non-oops_in_progress case, your version and the
> merged version are 100% identical - see
So they are, sorry the one that differs was the original Red Hat
Enterprise Linux patch.
> I don't have the initial email from ysgrifennodd gouji, and neither
> do the lkml archives. What's the problem?
Sysrq for one
prev parent reply other threads:[~2006-06-19 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000d01c6934c$f25c9870$f4647c0a@GOUJI>
2006-06-19 9:23 ` Alan Cox
2006-06-19 9:32 ` Russell King
2006-06-19 10:31 ` Alan Cox [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=1150713102.2871.1.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=gouji.masayuki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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
Powered by JetHome