From: Eddie James <eajames@linux.vnet.ibm.com>
To: openbmc@lists.ozlabs.org
Cc: joel@jms.id.au, andrew@aj.id.au, "Edward A. James" <eajames@us.ibm.com>
Subject: [PATCH linux dev-4.10 v2 0/9] drivers: fsi: client fixes and refactor
Date: Fri, 29 Sep 2017 17:40:59 -0500 [thread overview]
Message-ID: <1506724868-13010-1-git-send-email-eajames@linux.vnet.ibm.com> (raw)
From: "Edward A. James" <eajames@us.ibm.com>
This series refactors the FSI client device drivers. It adds a number of fixes
discovered from bugs over the past several months. Most critically, it fixes
various race conditions in the unbind/remove pathway of the occ-hwmon, occ,
and sbefifo drivers.
Changes since v1:
* split into multiple patches.
* add memory management patch.
Edward A. James (9):
drivers: fsi: SBEFIFO: General clean-up
drivers: fsi: SBEFIFO: Fix probe() and remove()
drivers: fsi: SBEFIFO: check for xfr complete in read wait_event
drivers: fsi: occ: General clean-up
drivers: fsi: occ: Poll while receiving "command in progress"
drivers: fsi: occ: Add cancel to remove() and fix probe()
drivers: fsi: occ: Fix client memory management
drivers/hwmon/occ: Remove repeated ops for OCC command in progress
drivers: hwmon: occ: Cancel occ operations in remove()
drivers/fsi/fsi-sbefifo.c | 321 +++++++++++++++++++++++-------------------
drivers/fsi/occ.c | 336 ++++++++++++++++++++++++++------------------
drivers/hwmon/occ/p9_sbe.c | 47 ++++---
include/linux/fsi-sbefifo.h | 6 +-
include/linux/occ.h | 20 ++-
5 files changed, 421 insertions(+), 309 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-09-29 22:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 22:40 Eddie James [this message]
2017-09-29 22:41 ` [PATCH linux dev-4.10 v2 1/9] drivers: fsi: SBEFIFO: General clean-up Eddie James
2017-10-04 23:59 ` Andrew Jeffery
2017-10-05 15:11 ` Eddie James
2017-09-29 22:41 ` [PATCH linux dev-4.10 v2 2/9] drivers: fsi: SBEFIFO: Fix probe() and remove() Eddie James
2017-10-05 0:32 ` Andrew Jeffery
2017-10-05 15:15 ` Eddie James
2017-10-05 17:37 ` Eddie James
2017-09-29 22:41 ` [PATCH linux dev-4.10 v2 3/9] drivers: fsi: SBEFIFO: check for xfr complete in read wait_event Eddie James
2017-10-05 0:35 ` Andrew Jeffery
2017-09-29 22:41 ` [PATCH linux dev-4.10 v2 4/9] drivers: fsi: occ: General clean-up Eddie James
2017-10-05 0:37 ` Andrew Jeffery
2017-10-05 15:27 ` Eddie James
2017-09-29 22:41 ` [PATCH linux dev-4.10 v2 5/9] drivers: fsi: occ: Poll while receiving "command in progress" Eddie James
2017-10-05 1:01 ` Andrew Jeffery
2017-10-05 15:38 ` Eddie James
2017-10-05 23:24 ` Andrew Jeffery
2017-09-29 22:41 ` [PATCH linux dev-4.10 v2 6/9] drivers: fsi: occ: Add cancel to remove() and fix probe() Eddie James
2017-10-05 1:07 ` Andrew Jeffery
2017-10-05 16:02 ` Eddie James
2017-09-29 22:41 ` [PATCH linux dev-4.10 v2 7/9] drivers: fsi: occ: Fix client memory management Eddie James
2017-10-05 1:12 ` Andrew Jeffery
2017-09-29 22:41 ` [PATCH linux dev-4.10 v2 8/9] drivers/hwmon/occ: Remove repeated ops for OCC command in progress Eddie James
2017-10-05 1:13 ` Andrew Jeffery
2017-09-29 22:41 ` [PATCH linux dev-4.10 v2 9/9] drivers: hwmon: occ: Cancel occ operations in remove() Eddie James
2017-10-05 1:20 ` Andrew Jeffery
2017-10-05 16:38 ` Eddie James
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=1506724868-13010-1-git-send-email-eajames@linux.vnet.ibm.com \
--to=eajames@linux.vnet.ibm.com \
--cc=andrew@aj.id.au \
--cc=eajames@us.ibm.com \
--cc=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.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 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.