From: Willy Tarreau <w@1wt.eu>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] staging: panel: pass correct lengths to keypad_send_key()
Date: Sat, 01 Dec 2012 08:13:22 +0000 [thread overview]
Message-ID: <20121201081322.GD25450@1wt.eu> (raw)
In-Reply-To: <20121129143835.GC12199@elgon.mountain>
On Fri, Nov 30, 2012 at 10:19:06AM +0100, walter harms wrote:
>
>
> Am 29.11.2012 15:38, schrieb Dan Carpenter:
> > We changed the sizeof() statements in 429ccf058b "staging:panel: Fixed
> > coding conventions." so that they could fit inside the 80 character
> > line limit. Unfortunately, the new sizeof() statements are a smaller
> > size. This reverts it.
> >
> > There isn't a nice way to stay within the 80 character limit without
> > a re-work so I've gone over.
> >
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > ---
> > Untested. The ->u.kbd.press_str and friends are funny data types. I'm
> > not sure how this code, works but the stuff we have is wrong and I've
> > reverted it back to the original.
> >
> > diff --git a/drivers/staging/panel/panel.c b/drivers/staging/panel/panel.c
> > index d9fec5b..dca42ce 100644
> > --- a/drivers/staging/panel/panel.c
> > +++ b/drivers/staging/panel/panel.c
> > @@ -1758,7 +1758,7 @@ static inline int input_state_high(struct logical_input *input)
> > char *press_str = input->u.kbd.press_str;
> > if (press_str[0])
> > keypad_send_key(press_str,
> > - sizeof(press_str));
> > + sizeof(input->u.kbd.press_str));
> > }
> yep, this looks like the original intention.
> NTL i would like to question the use of press_str and friends.
> Moving the if (press_str[0]) into keypad_send_key() seems
> more sensible.
Good point, I agree with you.
Willy
next prev parent reply other threads:[~2012-12-01 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 14:38 [patch] staging: panel: pass correct lengths to keypad_send_key() Dan Carpenter
2012-11-30 9:19 ` walter harms
2012-12-01 8:08 ` Willy Tarreau
2012-12-01 8:13 ` Willy Tarreau [this message]
2012-12-02 11:22 ` Dan Carpenter
2012-12-02 11:53 ` Willy Tarreau
2012-12-02 15:44 ` walter harms
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=20121201081322.GD25450@1wt.eu \
--to=w@1wt.eu \
--cc=kernel-janitors@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 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.