public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: rct@gherkin.frus.com (Bob_Tracy)
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: weird application breakage in 2.5.2-pre5
Date: Sun, 6 Jan 2002 19:48:57 -0600 (CST)	[thread overview]
Message-ID: <m16NOuH-0005khC@gherkin.frus.com> (raw)
In-Reply-To: <20020103172641.D6267@suse.de> "from Jens Axboe at Jan 3, 2002 05:26:41 pm"

Jens Axboe wrote:
> On Thu, Jan 03 2002, Bob_Tracy wrote:
> > The application is elm2.4.ME+.82 with PGP 6.5.8.  Works fine under
> > kernel version 2.4.17.
> 
> very unlikely I would say, maybe it's an odd scheduler interaction?

I'm happy to report that everything seems to be working fine with
2.5.2-pre9.

-- 
-----------------------------------------------------------------------
Bob Tracy                   WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------

      reply	other threads:[~2002-01-07  1:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-03 14:49 weird application breakage in 2.5.2-pre5 Bob_Tracy
2002-01-03 16:26 ` Jens Axboe
2002-01-07  1:48   ` Bob_Tracy [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=m16NOuH-0005khC@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=axboe@suse.de \
    --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