From: Arnd Bergmann <arnd@arndb.de>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Jiri Kosina <jikos@kernel.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, arnd@arndb.de
Subject: [PATCH 0/5] HID: intel_ish-hid: various cleanups
Date: Tue, 16 May 2017 13:09:02 +0200 [thread overview]
Message-ID: <20170516110907.3545799-1-arnd@arndb.de> (raw)
Hi,
I ran into a warning message during randconfig testing and spent way
too much time figuring out how to best address it. One thing led to
another and I ended up with a 5 patch series.
Please have a look at the first patch separately, it might fix an
important bug and need backporting to stable kernels, or it might
only address a harmless warning.
For the rest of the patches, please merge for 4.13 unless you
see something wrong.
Arnd
[PATCH 1/5] HID: intel_ish-hid: fix potential uninitialized data
[PATCH 2/5] HID: intel_ish-hid: clarify locking in client code
[PATCH 3/5] HID: intel_ish-hid: convert timespec to ktime_t
[PATCH 4/5] HID: intel_ish-hid: fix format string for size_t
[PATCH 5/5] HID: intel_ish-hid: enable compile testing
next reply other threads:[~2017-05-16 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 11:09 Arnd Bergmann [this message]
2017-05-16 11:09 ` [PATCH 1/5] HID: intel_ish-hid: fix potential uninitialized data usage Arnd Bergmann
2017-05-17 19:44 ` Arnd Bergmann
2017-05-16 11:09 ` [PATCH 2/5] HID: intel_ish-hid: clarify locking in client code Arnd Bergmann
2017-05-16 11:09 ` [PATCH 3/5] HID: intel_ish-hid: convert timespec to ktime_t Arnd Bergmann
2017-05-16 11:09 ` [PATCH 4/5] HID: intel_ish-hid: fix format string for size_t Arnd Bergmann
2017-05-16 11:09 ` [PATCH 5/5] HID: intel_ish-hid: enable compile testing Arnd Bergmann
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=20170516110907.3545799-1-arnd@arndb.de \
--to=arnd@arndb.de \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.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
all inboxes | Powered by JetHome®