From: "Michal Suchánek" <msuchanek@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/9] usb_kdb: only process events succesfully received
Date: Wed, 3 Jul 2019 11:11:19 +0200 [thread overview]
Message-ID: <20190703111119.1e5be70e@naga> (raw)
In-Reply-To: <CAEUhbmUpsKYiBq1+TFH_nYPqnU=FCwXjh8Vbk=a+PF1R7M-x5A@mail.gmail.com>
On Wed, 3 Jul 2019 09:37:42 +0800
Bin Meng <bmeng.cn@gmail.com> wrote:
> Hi Michal,
>
> On Wed, Jul 3, 2019 at 1:57 AM Michal Suchanek <msuchanek@suse.de> wrote:
> >
> > On error the data buffer does not contain valid data so do not submit it
> > for processing. Usually it will contain the last data recieved so the
> > last pressed key will be repeated indefinitely on device failure.
> >
> > Signed-off-by: Michal Suchanek <msuchanek@suse.de>
> > ---
> > v2: fix indentation
> > ---
> > common/usb_kbd.c | 7 +++----
> > 1 file changed, 3 insertions(+), 4 deletions(-)
> >
> > diff --git a/common/usb_kbd.c b/common/usb_kbd.c
> > index 020f0d4117f7..74206d2de74f 100644
> > --- a/common/usb_kbd.c
> > +++ b/common/usb_kbd.c
> > @@ -317,10 +317,9 @@ static inline void usb_kbd_poll_for_event(struct usb_device *dev)
> > struct usb_kbd_pdata *data = dev->privptr;
> >
> > /* Submit a interrupt transfer request */
> > - usb_submit_int_msg(dev, data->intpipe, &data->new[0], data->intpktsize,
> > - data->intinterval);
> > -
> > - usb_kbd_irq_worker(dev);
> > + if (!usb_submit_int_msg(dev, data->intpipe, &data->new[0],
> > + data->intpktsize, data->intinterval))
>
> The indentation still looks incorrect. It should align to one
> character after the open parenthesis.
It looks correct after the function is renamed twice in following
patches.
>
> > + usb_kbd_irq_worker(dev);
Anyway, the problem I was referring to was excessive indentation of
this line in previous version of the patch.
Thanks
Michal
next prev parent reply other threads:[~2019-07-03 9:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 17:55 [U-Boot] [PATCH v2 1/9] usb: r8a66597: return -ENOTSUPP from unimplemented submit_int_msg Michal Suchanek
2019-07-02 17:55 ` [U-Boot] [PATCH v2 2/9] usb: sl811-hcd: " Michal Suchanek
2019-07-02 18:41 ` Marek Vasut
2019-07-02 19:35 ` Michal Suchánek
2019-07-02 21:20 ` Marek Vasut
2019-07-04 16:00 ` Michal Suchánek
2019-07-04 16:19 ` Marek Vasut
2019-07-04 18:54 ` Michal Suchánek
2019-07-04 19:05 ` Marek Vasut
2019-07-04 19:15 ` Michal Suchánek
2019-07-02 17:55 ` [U-Boot] [PATCH v2 3/9] usb_kdb: only process events succesfully received Michal Suchanek
2019-07-03 1:37 ` Bin Meng
2019-07-03 9:11 ` Michal Suchánek [this message]
2019-07-02 17:55 ` [U-Boot] [PATCH v2 4/9] usb: usb_submit_int_msg -> usb_int_msg Michal Suchanek
2019-07-02 17:55 ` [U-Boot] [PATCH v2 5/9] usb: storage: submit_int_msg " Michal Suchanek
2019-07-03 1:39 ` Bin Meng
2019-07-04 16:01 ` Michal Suchánek
2019-07-05 1:34 ` Bin Meng
2019-07-02 17:55 ` [U-Boot] [PATCH v2 6/9] usb: Add nonblock argument to submit_int_msg Michal Suchanek
2019-07-02 17:55 ` [U-Boot] [PATCH v2 7/9] usb: add usb_int_msg_nonblock Michal Suchanek
2019-07-02 17:55 ` [U-Boot] [PATCH v2 8/9] usb: kbd: use usb_int_msg_nonblock for polling Michal Suchanek
2019-07-02 17:55 ` [U-Boot] [PATCH v2 9/9] dwc2: use the nonblock argument in submit_int_msg Michal Suchanek
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=20190703111119.1e5be70e@naga \
--to=msuchanek@suse.de \
--cc=u-boot@lists.denx.de \
/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