linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-fbdev-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbdev: Fix return error of fb_write
Date: Mon, 17 Apr 2006 15:45:10 +0100	[thread overview]
Message-ID: <1145285110.6199.22.camel@localhost.localdomain> (raw)
In-Reply-To: <444086CB.2000700@gmail.com>

On Sat, 2006-04-15 at 13:38 +0800, Antonino A. Daplas wrote:
> Fix return code of fb_write():
> 
> If at least 1 byte was transferred to the device, return number of bytes,
> otherwise:
> 
>     - return -EFBIG - if file offset is past the maximum allowable offset or
>       size is greater than framebuffer length
>     - return -ENOSPC - if size is greater than framebuffer length - offset
> 
> Signed-off-by: Antonino Daplas <adaplas@pol.net>

I can confirm this fixes the problem I reported, thanks!

Richard



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

      reply	other threads:[~2006-04-17 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14 10:16 Behaviour change of /dev/fb0? Richard Purdie
2006-04-14 23:29 ` [Linux-fbdev-devel] " Antonino A. Daplas
2006-04-15  0:13   ` Richard Purdie
2006-04-15  0:53 ` Antonino A. Daplas
2006-04-15  4:31   ` Andrew Morton
2006-04-15  5:38     ` [PATCH] fbdev: Fix return error of fb_write Antonino A. Daplas
2006-04-17 14:45       ` Richard Purdie [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=1145285110.6199.22.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=adaplas@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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;
as well as URLs for NNTP newsgroup(s).