From: Michael Buesch <freesoftwaredeveloper@web.de>
To: dick.streefland@altium.nl (Dick Streefland)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.66 oops
Date: Wed, 2 Apr 2003 13:39:27 +0200 [thread overview]
Message-ID: <200304021339.27977.freesoftwaredeveloper@web.de> (raw)
In-Reply-To: <3862.3e8ab21c.73a7f@altium.nl>
On Wednesday 02 April 2003 11:49, Dick Streefland wrote:
> This is probably the same oops as I reported saturday (Subject:
> [2.5.66] Oops in bttv driver). I got a reply from Greg KH that the
> problem is fixed in the latest bk tree.
Thanks, I was unsubscribed from linux-kernel, so I didn't knew that. :)
Regards Michael Buesch.
--
-------------
My homepage: http://www.8ung.at/tuxsoft
fighting for peace is like fu**ing for virginity
next prev parent reply other threads:[~2003-04-02 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 18:32 2.5.66 oops Michael Buesch
2003-04-01 18:42 ` Michael Buesch
2003-04-02 9:49 ` Dick Streefland
2003-04-02 11:39 ` Michael Buesch [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-05 23:02 2.5.66 OOPS Grzegorz Jaskiewicz
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=200304021339.27977.freesoftwaredeveloper@web.de \
--to=freesoftwaredeveloper@web.de \
--cc=dick.streefland@altium.nl \
--cc=linux-kernel@vger.kernel.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