All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Axel Kittenberger <Axel.Kittenberger@maxxio.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
	Axel Kittenberger <Axel.Kittenberger@maxxio.at>,
	linux-kernel@vger.kernel.org
Subject: Re: Patch, forward release() return values to the close() call
Date: Fri, 22 Mar 2002 03:53:21 -0500	[thread overview]
Message-ID: <20020322035321.B8052@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1016697001.29134.linux-kernel2news@redhat.com> <200203211845.g2LIjTu22218@devserv.devel.redhat.com> <200203220806.JAA10107@merlin.gams.co.at>

> From: Axel Kittenberger <Axel.Kittenberger@maxxio.com>
> Date: Fri, 22 Mar 2002 09:06:38 +0100

>[...]
> So when closing a file with write-behind cache, close() signals in example an 
> error (it """fails"""), as application I do not have close it again or to 
> circle, but I have to live with the fact that something went wrong, [...]

I do not think it's true. And what about exit()?

-- Pete

  reply	other threads:[~2002-03-22  8:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1016697001.29134.linux-kernel2news@redhat.com>
     [not found] ` <200203211845.g2LIjTu22218@devserv.devel.redhat.com>
2002-03-22  8:06   ` Patch, forward release() return values to the close() call Axel Kittenberger
2002-03-22  8:53     ` Pete Zaitcev [this message]
2002-03-21  7:47 Axel Kittenberger
2002-03-21  8:13 ` Jeff Garzik
2002-03-21 16:32   ` David Brown
2002-03-22  7:58     ` Axel Kittenberger
2002-03-22 13:51       ` David Brown
2002-03-25  9:50         ` Axel Kittenberger
2002-03-25 13:33           ` David Brown
2002-03-26  8:52             ` Axel Kittenberger
2002-03-21  8:21 ` Jeff Garzik
2002-03-21  8:27 ` Jeff Garzik
2002-03-21  9:10   ` Oliver Neukum
2002-03-21  9:18     ` Jeff Garzik
2002-03-21 10:14       ` Oliver.Neukum

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=20020322035321.B8052@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=Axel.Kittenberger@maxxio.at \
    --cc=Axel.Kittenberger@maxxio.com \
    --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 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.