From: Jens Axboe <axboe@suse.de>
To: Momchil Velikov <velco@fadata.bg>
Cc: Ralf Oehler <R.Oehler@GDAmbH.com>,
Scsi <linux-scsi@vger.kernel.org>,
linux-kernel@vger.kernel.org, Andrea Arcangeli <andrea@suse.de>,
Jens Axboe <axboe@kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: one-line-patch against SCSI-Read-Error-BUG()
Date: Tue, 5 Feb 2002 15:42:34 +0100 [thread overview]
Message-ID: <20020205154234.B16105@suse.de> (raw)
In-Reply-To: <XFMail.20020205153210.R.Oehler@GDAmbH.com> <20020205152434.A16105@suse.de> <871yg07zg4.fsf@fadata.bg>
In-Reply-To: <871yg07zg4.fsf@fadata.bg>
On Tue, Feb 05 2002, Momchil Velikov wrote:
> >>>>> "Jens" == Jens Axboe <axboe@suse.de> writes:
>
> Jens> On Tue, Feb 05 2002, Ralf Oehler wrote:
> >> Hi, List
> >>
> >> I think, I found a very simple solution for this annoying BUG().
>
> Jens> You fail to understand that the BUG triggering indicates that their is a
> Jens> BUG _somewhere_ -- the triggered BUG is not the bug itself, of course,
> Jens> that would be stupid :-)
>
> Erm, having a BUG() somewhere can be a bug by itself ;)
>
> I think that's what he meant (regardless if he was right or not).
Of course it can, any statement can be a bug. That's hardly the point
:-)
--
Jens Axboe
next prev parent reply other threads:[~2002-02-05 15:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 14:32 one-line-patch against SCSI-Read-Error-BUG() Ralf Oehler
2002-02-05 14:24 ` Jens Axboe
2002-02-05 14:52 ` Momchil Velikov
2002-02-05 14:42 ` Jens Axboe [this message]
2002-02-06 4:40 ` Douglas Gilbert
2002-02-05 20:56 ` Alan Cox
2002-02-06 7:32 ` Ralf Oehler
2002-02-06 9:22 ` Helge Hafting
2002-02-05 22:40 ` James Stevenson
2002-02-06 7:36 ` Ralf Oehler
2002-02-07 0:59 ` Patrick Mansfield
2002-02-07 5:10 ` Douglas Gilbert
2002-02-07 7:29 ` Jens Axboe
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=20020205154234.B16105@suse.de \
--to=axboe@suse.de \
--cc=R.Oehler@GDAmbH.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=axboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=velco@fadata.bg \
/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