From: Johannes Berg <johannes@sipsolutions.net>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [OOPS] 2.6.17-rc3 on an mpc8241
Date: Thu, 15 Jun 2006 00:27:39 +0200 [thread overview]
Message-ID: <1150324059.13958.30.camel@johannes.berg> (raw)
In-Reply-To: <Pine.LNX.4.60.0606150017380.12545@poirot.grange>
[-- Attachment #1: Type: text/plain, Size: 222 bytes --]
On Thu, 2006-06-15 at 00:25 +0200, Guennadi Liakhovetski wrote:
> As I said - already reported and fixed in 2.6.17-rc6:
Ah, I saw that but didn't make the connection. Sorry. Good to know it's
fine now.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
prev parent reply other threads:[~2006-06-14 22:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 20:48 [OOPS] 2.6.17-rc3 on an mpc8241 Guennadi Liakhovetski
2006-06-14 20:57 ` Johannes Berg
2006-06-14 21:01 ` Guennadi Liakhovetski
2006-06-14 22:08 ` Guennadi Liakhovetski
2006-06-14 22:11 ` Johannes Berg
2006-06-14 22:25 ` Guennadi Liakhovetski
2006-06-14 22:27 ` Johannes Berg [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=1150324059.13958.30.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=g.liakhovetski@gmx.de \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).