All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Shivani Bhardwaj <shivanib134@gmail.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] Staging: xgifb: XGI_main_26: Remove unused code
Date: Mon, 12 Oct 2015 16:14:52 +0530	[thread overview]
Message-ID: <20151012104452.GE13596@sudip-pc> (raw)
In-Reply-To: <CAKHNQQHhftvBwJ+6ACmA-MgvaqRbwXhsCHyP8Wpc=wwQVg2wbw@mail.gmail.com>

On Mon, Oct 12, 2015 at 03:28:33PM +0530, Shivani Bhardwaj wrote:
> On Mon, Oct 12, 2015 at 2:52 PM, Julia Lawall <julia.lawall@lip6.fr> wrote:
> > On Mon, 12 Oct 2015, Shivani Bhardwaj wrote:
> >
> >> Remove unused variable and its occurences as it is not used anywhere in
> >> the code.
> >> Issue found using coccinelle.
> >>
> >> Signed-off-by: Shivani Bhardwaj <shivanib134@gmail.com>
> >> ---
> >>
> >> -     /* Calculation wrong for 1024x600 - force it to 60Hz */
> >> -     if ((var->xres == 1024) && (var->yres == 600))
> >> -             refresh_rate = 60;
> >
> > Could it be supposed to be xgifb_info->refresh_rate = 60; ?
> >
> > julia
> >
> 
> Won't that be a part of structure whose object is xgifb_info? This is
> any normal int type. Plus, it doesn't give any errors when removed, it
> should have if it were xgifb_info's member. Please correct me if I  am
> wrong.

From C syntax point of view your patch is correct. But looking at the
comment mentioned there this could have been:

diff --git a/drivers/staging/xgifb/XGI_main_26.c b/drivers/staging/xgifb/XGI_main_26.c
index 5a6251a4..0436dbe 100644
--- a/drivers/staging/xgifb/XGI_main_26.c
+++ b/drivers/staging/xgifb/XGI_main_26.c
@@ -1230,7 +1230,7 @@ static int XGIfb_check_var(struct fb_var_screeninfo *var, struct fb_info *info)
 	unsigned int vtotal = 0;
 	unsigned int drate = 0, hrate = 0;
 	int found_mode = 0;
-	int refresh_rate, search_idx;
+	int search_idx;
 
 	if ((var->vmode & FB_VMODE_MASK) == FB_VMODE_NONINTERLACED) {
 		vtotal = var->upper_margin + var->yres + var->lower_margin
@@ -1268,7 +1268,7 @@ static int XGIfb_check_var(struct fb_var_screeninfo *var, struct fb_info *info)
 
 	/* Calculation wrong for 1024x600 - force it to 60Hz */
 	if ((var->xres == 1024) && (var->yres == 600))
-		refresh_rate = 60;
+		xgifb_info->refresh_rate = 60;
 
 	search_idx = 0;
 	while ((XGIbios_mode[search_idx].mode_no != 0) &&

---
Maybe this was the actual intention of the developer as there is also
another global static variable named as refresh_rate which is having the
refresh frequency and saving the Hz value in xgifb_info->refresh_rate.
But that part is in the probe function and the probe will be called
before fb_check_var callback.
Anyways, this was just a thought, please donot send v2 based on this.
Let Greg see it first.

regards
sudip


  reply	other threads:[~2015-10-12 10:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12  9:09 [PATCH] Staging: xgifb: XGI_main_26: Remove unused code Shivani Bhardwaj
2015-10-12  9:22 ` [Outreachy kernel] " Julia Lawall
2015-10-12  9:58   ` Shivani Bhardwaj
2015-10-12 10:44     ` Sudip Mukherjee [this message]
2015-10-12 11:26       ` Julia Lawall

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=20151012104452.GE13596@sudip-pc \
    --to=sudipm.mukherjee@gmail.com \
    --cc=julia.lawall@lip6.fr \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=shivanib134@gmail.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.