From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linux-input@vger.kernel.org,
Andrey Konovalov <andreyknvl@google.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 0/2] Input-gtco: Adjustments for gtco_probe()
Date: Wed, 24 Jan 2018 16:13:25 +0100 [thread overview]
Message-ID: <5c4410ab-5174-ce8d-cab6-7979aa61f996@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Wed, 24 Jan 2018 15:26:56 +0100
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation
Improve a size determination
drivers/input/tablet/gtco.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--
2.16.1
next reply other threads:[~2018-01-24 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 15:13 SF Markus Elfring [this message]
2018-01-24 15:14 ` [PATCH 1/2] Input: gtco: Delete an error message for a failed memory allocation in gtco_probe() SF Markus Elfring
2018-01-24 15:15 ` [PATCH 2/2] Input: gtco: Improve a size determination " SF Markus Elfring
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=5c4410ab-5174-ce8d-cab6-7979aa61f996@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=andreyknvl@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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 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).