LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ben Dooks <ben@fluff.org.uk>,
	Linux Frame Buffer Device Development 
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] [PATCH] fb: sm501fb off-by-1 sysfs store
Date: Thu, 1 Mar 2007 22:35:28 +0900	[thread overview]
Message-ID: <20070301133528.GA6504@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0703011423060.766@pademelon.sonytel.be>

On Thu, Mar 01, 2007 at 02:25:55PM +0100, Geert Uytterhoeven wrote:
> On Thu, 1 Mar 2007, Paul Mundt wrote:
> > @@ -1074,9 +1074,9 @@ static ssize_t sm501fb_crtsrc_store(struct device *dev,
> >  	if (len < 1)
> >  		return -EINVAL;
> >  
> > -	if (strnicmp(buf, "crt", sizeof("crt")) == 0)
> > +	if (strnicmp(buf, "crt", 3) == 0)
> >  		head = HEAD_CRT;
> > -	else if (strnicmp(buf, "panel", sizeof("panel")) == 0)
> > +	else if (strnicmp(buf, "panel", 5) == 0)
> >  		head = HEAD_PANEL;
> >  	else
> >  		return -EINVAL;
> 
> What about using just `strlen("string")' instead? ISTR gcc optimizes this to a
> constant. Not that it matters that much, as the actual string won't be
> duplicated.
> 
I stuck with the constants since they were already referenced in the
function, and there are enough other places in the kernel where they're
used for these things. I didn't figure that 5 was a terribly high number
to count to, but if there's expected difficulty, strlen() is of course an
option.

Personally I find it less visually offensive with constants, but as long
as the end number is the same, I'm not too concerned with how we get
there. Feel free to change it if you wish.

      reply	other threads:[~2007-03-01 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01  8:24 Paul Mundt
2007-03-01  9:16 ` Ben Dooks
2007-03-01 13:25 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2007-03-01 13:35   ` Paul Mundt [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=20070301133528.GA6504@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=ben@fluff.org.uk \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [Linux-fbdev-devel] [PATCH] fb: sm501fb off-by-1 sysfs store' \
    /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

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).