From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: cpaul@redhat.com
Cc: David Herrmann <dh.herrmann@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org, linux-api@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Greg KH <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>, Joe Perches <joe@perches.com>,
Jiri Slaby <jslaby@suse.com>,
Vishnu Patekar <vishnupatekar0510@gmail.com>,
Sebastian Ott <sebott@linux.vnet.ibm.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Hans de Goede <hdegoede@redhat.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v6.1 1/1] Input: Add userio module
Date: Fri, 2 Oct 2015 10:37:14 -0700 [thread overview]
Message-ID: <20151002173714.GA8437@dtor-ws> (raw)
In-Reply-To: <1443030899-28737-1-git-send-email-cpaul@redhat.com>
On Wed, Sep 23, 2015 at 01:54:59PM -0400, cpaul@redhat.com wrote:
> +static int userio_device_write(struct serio *id, unsigned char val)
> +{
> + struct userio_device *userio = id->port_data;
> + unsigned long flags;
> +
> + if (!userio)
> + return -1;
I still have the same question: how can this happen? Where do we reset
port data to NULL? What happens if we set to NULL after checking?
> +
> + spin_lock_irqsave(&userio->buf_lock, flags);
> +
> + userio->buf[userio->head] = val;
> + userio->head = (userio->head + 1) % USERIO_BUFSIZE;
> +
> + if (userio->head == userio->tail)
> + dev_warn(userio_misc.this_device,
> + "Buffer overflowed, userio client isn't keeping up");
> +
> + spin_unlock_irqrestore(&userio->buf_lock, flags);
> +
> + wake_up_interruptible(&userio->waitq);
> +
> + return 0;
> +}
Thanks.
--
Dmitry
next prev parent reply other threads:[~2015-10-02 17:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 23:00 [PATCH v5] Input: Add userio module cpaul
2015-09-19 17:39 ` Dmitry Torokhov
2015-09-22 10:59 ` David Herrmann
2015-09-23 17:49 ` [PATCH v6 1/1] " cpaul
[not found] ` <1443030589-27574-1-git-send-email-cpaul-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-23 17:54 ` [PATCH v6.1 " cpaul-H+wXaHxf7aLQT0dZR+AlfA
2015-10-02 17:37 ` Dmitry Torokhov [this message]
2015-10-05 14:06 ` Stephen Chandler Paul
2015-10-23 20:47 ` [PATCH v6.2 " cpaul
2015-10-24 22:40 ` Dmitry Torokhov
2015-10-26 13:51 ` Lyude
2015-10-26 23:26 ` Dmitry Torokhov
2015-10-27 18:10 ` Lyude
2015-10-28 2:01 ` Dmitry Torokhov
2015-10-05 15:55 ` [PATCH v7] " cpaul
2015-10-08 17:20 ` David Herrmann
[not found] ` <CANq1E4RCwq49T=iR40NfQLtxKdLCoTLFQB2KA17ksqRyTB568w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-09 14:30 ` [PATCH v8] " cpaul-H+wXaHxf7aLQT0dZR+AlfA
2015-10-09 14:52 ` LABBE Corentin
2015-10-09 14:59 ` Stephen Chandler Paul
2015-10-24 22:26 ` [PATCH v7] " Dmitry Torokhov
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=20151002173714.GA8437@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=benjamin.tissoires@redhat.com \
--cc=cpaul@redhat.com \
--cc=dh.herrmann@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=joe@perches.com \
--cc=jslaby@suse.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=sebott@linux.vnet.ibm.com \
--cc=vishnupatekar0510@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 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).