From: Luiz Capitulino <lcapitulino@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: alevy@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 6/9] omap_lcdc: omap_ppm_save(): add error handling
Date: Thu, 30 Aug 2012 08:38:37 -0300 [thread overview]
Message-ID: <20120830083837.2f550c0f@doriath.home> (raw)
In-Reply-To: <CAFEAcA-w_PX2nUKH4_vxST-6AzOKCE=hyoMAOacaZ4gZmNGqDw@mail.gmail.com>
On Wed, 29 Aug 2012 22:28:38 +0100
Peter Maydell <peter.maydell@linaro.org> wrote:
> On 29 August 2012 20:53, Luiz Capitulino <lcapitulino@redhat.com> wrote:
> > Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> > ---
> > hw/omap_lcdc.c | 59 ++++++++++++++++++++++++++++++++++++++++++++--------------
> > 1 file changed, 45 insertions(+), 14 deletions(-)
> >
> > diff --git a/hw/omap_lcdc.c b/hw/omap_lcdc.c
> > index 3d6328f..e2ba108 100644
> > --- a/hw/omap_lcdc.c
> > +++ b/hw/omap_lcdc.c
> > @@ -224,18 +224,24 @@ static void omap_update_display(void *opaque)
> > omap_lcd->invalidate = 0;
> > }
> >
> > -static int omap_ppm_save(const char *filename, uint8_t *data,
> > - int w, int h, int linesize)
> > +static void omap_ppm_save(const char *filename, uint8_t *data,
> > + int w, int h, int linesize, Error **errp)
> > {
> > FILE *f;
> > uint8_t *d, *d1;
> > unsigned int v;
> > - int y, x, bpp;
> > + int ret, y, x, bpp;
> >
> > f = fopen(filename, "wb");
> > - if (!f)
> > - return -1;
> > - fprintf(f, "P6\n%d %d\n%d\n", w, h, 255);
> > + if (!f) {
> > + error_setg(errp, "failed to open file '%s': %s", filename,
> > + strerror(errno));
> > + return;
> > + }
> > + ret = fprintf(f, "P6\n%d %d\n%d\n", w, h, 255);
> > + if (ret < 0) {
> > + goto write_err;
> > + }
>
> We don't use 'ret' in write_err, so why not just
> if (fprintf(f....) < 0) {
> goto write_err;
> }
>
> here and similarly below and drop the variable altogether?
For clarity. This is probably a matter of taste, but I much more prefer
separate statements (vs. saving 4 bytes during the function call).
next prev parent reply other threads:[~2012-08-30 11:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 19:52 [Qemu-devel] [PATCH qmp-next v3 0/9]: qapi: convert screendump Luiz Capitulino
2012-08-29 19:52 ` [Qemu-devel] [PATCH 1/9] error: add error_setg() Luiz Capitulino
2012-08-29 19:52 ` [Qemu-devel] [PATCH 2/9] console: vga_hw_screen_dump_ptr: take Error argument Luiz Capitulino
2012-08-29 19:53 ` [Qemu-devel] [PATCH 3/9] qapi: convert screendump Luiz Capitulino
2012-08-29 19:53 ` [Qemu-devel] [PATCH 4/9] vga: ppm_save(): add error handling Luiz Capitulino
2012-08-29 19:53 ` [Qemu-devel] [PATCH 5/9] omap_lcdc: rename ppm_save() to omap_ppm_save() Luiz Capitulino
2012-08-29 21:26 ` Peter Maydell
2012-08-29 19:53 ` [Qemu-devel] [PATCH 6/9] omap_lcdc: omap_ppm_save(): add error handling Luiz Capitulino
2012-08-29 21:28 ` Peter Maydell
2012-08-30 11:38 ` Luiz Capitulino [this message]
2012-08-29 19:53 ` [Qemu-devel] [PATCH 7/9] g364fb: g364fb_screen_dump(): " Luiz Capitulino
2012-08-29 19:53 ` [Qemu-devel] [PATCH 8/9] tcx: tcx24_screen_dump(): " Luiz Capitulino
2012-08-29 19:53 ` [Qemu-devel] [PATCH 9/9] tcx: tcx_screen_dump(): " Luiz Capitulino
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=20120830083837.2f550c0f@doriath.home \
--to=lcapitulino@redhat.com \
--cc=alevy@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).