From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Fabio Estevam <fabio.estevam@freescale.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
"H. Nikolaus Schaller" <hns@goldelico.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pyra-handheld.com, letux-kernel@openphoenux.org
Subject: [PATCH v2 0/4] fixes for twl6040-vibra
Date: Thu, 21 Apr 2016 13:43:46 +0200 [thread overview]
Message-ID: <cover.1461239029.git.hns@goldelico.com> (raw)
Changes V2:
* remove 2 patches already accepted
* keep DT memory management patch until we know if there is a better solution in the library
* suggestions by Dmitry Torokhov:
* add cancel_work to make removal of mutex safe
* replace "unregister handler" patch by "do not reparent" patch
* new: add fix for atomic schedule bug
V1: 2016-04-18 21:55:44: There are some small bugs in the twl6040-vibra driver and differences to how twl4030 vibra works.
This patch series addresses them.
Dmitry Torokhov (1):
Input: twl6040-vibra - do not reparent to grandparent
H. Nikolaus Schaller (3):
input: twl6040-vibra: fix DT node memory management
input: twl6040-vibra: remove mutex
input: twl6040-vibra: fix atomic schedule panic
drivers/input/misc/twl6040-vibra.c | 31 ++++++++++---------------------
1 file changed, 10 insertions(+), 21 deletions(-)
--
2.7.3
next reply other threads:[~2016-04-21 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 11:43 H. Nikolaus Schaller [this message]
2016-04-21 11:43 ` [PATCH v2 1/4] input: twl6040-vibra: fix DT node memory management H. Nikolaus Schaller
2016-04-21 11:43 ` [PATCH v2 2/4] input: twl6040-vibra: remove mutex H. Nikolaus Schaller
2016-04-21 11:43 ` [PATCH v2 3/4] Input: twl6040-vibra - do not reparent to grandparent H. Nikolaus Schaller
2016-04-21 11:43 ` [PATCH v2 4/4] input: twl6040-vibra: fix atomic schedule panic H. Nikolaus Schaller
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=cover.1461239029.git.hns@goldelico.com \
--to=hns@goldelico.com \
--cc=dmitry.torokhov@gmail.com \
--cc=fabio.estevam@freescale.com \
--cc=kernel@pyra-handheld.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@ti.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 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.