mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Cherry <cherry@osdl.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: IA32 - 6 New warnings (gcc 3.2.2)
Date: 26 Sep 2003 13:37:06 -0700	[thread overview]
Message-ID: <1064608625.10304.52.camel@cherrytest.pdx.osdl.net> (raw)
In-Reply-To: <20030926155654.GO15696@fs.tum.de>


On Fri, 2003-09-26 at 08:56, Adrian Bunk wrote:
> On Thu, Sep 25, 2003 at 10:48:35PM -0700, John Cherry wrote:
> >...
> > drivers/char/drm/sis_mm.c:92: warning: unused variable `req'
> >...
> 
> Looking at the code, this seems to be a bogus warning in the gcc version
> you are using.
> 
> cu
> Adrian

Yes, this warning looks bogus.  Hard to understand why this was flagged
as a warning by gcc 3.2.2...

int sis_fb_alloc( DRM_IOCTL_ARGS )
{
        drm_sis_mem_t fb;
-->     struct sis_memreq req;
        int retval = 0;
                                                                                
        DRM_COPY_FROM_USER_IOCTL(fb, (drm_sis_mem_t *)data, sizeof(fb));
                                                                                
        req.size = fb.size;
-->     sis_malloc(&req);
        if (req.offset) {
                /* TODO */
                fb.offset = req.offset;
                fb.free = req.offset;
                if (!add_alloc_set(fb.context, VIDEO_TYPE, fb.free)) {
                        DRM_DEBUG("adding to allocation set fails\n");
                        sis_free(req.offset);
                        retval = DRM_ERR(EINVAL);
                }
        } else {
                fb.offset = 0;
                fb.size = 0;
                fb.free = 0;
        }
<snip>

John



  reply	other threads:[~2003-09-26 20:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-26  5:48 John Cherry
2003-09-26 15:56 ` Adrian Bunk
2003-09-26 20:37   ` John Cherry [this message]
2003-09-26 21:13     ` John Cherry
2003-09-26 21:49       ` Adrian Bunk

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=1064608625.10304.52.camel@cherrytest.pdx.osdl.net \
    --to=cherry@osdl.org \
    --cc=bunk@fs.tum.de \
    --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

all inboxes | Powered by JetHome®