From: Rainer Weikusat <rainer.weikusat@sncag.com>
To: Rainer Weikusat <rweikusat@sncag.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Implementation defined behaviour in read_write.c
Date: Tue, 21 Sep 2004 13:43:51 +0800 [thread overview]
Message-ID: <874qlsfa7c.fsf@farside.sncag.com> (raw)
In-Reply-To: <878yb5ey11.fsf@farside.sncag.com> (Rainer Weikusat's message of "Mon, 20 Sep 2004 23:54:34 +0800")
Rainer Weikusat <rweikusat@sncag.com> writes:
> + if (tot_len != cur_len) goto out;
... and this is of course rubbish ... both tests (ie <0 and !=)
next prev parent reply other threads:[~2004-09-21 5:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 15:54 Implementation defined behaviour in read_write.c Rainer Weikusat
2004-09-21 5:43 ` Rainer Weikusat [this message]
2004-09-21 10:57 ` Alan Cox
2004-09-22 5:58 ` Rainer Weikusat
2004-09-22 14:41 ` Linus Torvalds
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=874qlsfa7c.fsf@farside.sncag.com \
--to=rainer.weikusat@sncag.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rweikusat@sncag.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.