From: Richard Acayan <mailingradian@gmail.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Amol Maheshwari <amahesh@qti.qualcomm.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Richard Acayan <mailingradian@gmail.com>
Subject: [PATCH v2 0/2] misc: fastrpc: Fixes for issues in userspace
Date: Mon, 27 Mar 2023 17:02:16 -0400 [thread overview]
Message-ID: <20230327210217.60948-1-mailingradian@gmail.com> (raw)
Changes since v1 (20230130222716.7016-1-mailingradian@gmail.com):
- use /* */ for comments (2/2)
- exclude demonstration from final commit message (2/2)
- accumulate review tags (1-2/2)
Hi everyone,
I've been playing around a bit with the FastRPC ioctl interface on the
Pixel 3a with some device tree patches. I was testing on a device tree
that caused the ADSP to crash every 10 seconds, and the inconvenience
caused by related bugs encouraged me to write a few fixes. A
demonstration is provided in patch 2.
Please enjoy and review these patches for better userspace while remote
processors crash.
Richard Acayan (2):
misc: fastrpc: return -EPIPE to invocations on device removal
misc: fastrpc: reject new invocations during device removal
drivers/misc/fastrpc.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
--
2.40.0
next reply other threads:[~2023-03-27 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 21:02 Richard Acayan [this message]
2023-03-27 21:02 ` [PATCH v2 1/2] misc: fastrpc: return -EPIPE to invocations on device removal Richard Acayan
2023-03-27 21:02 ` [PATCH v2 2/2] misc: fastrpc: reject new invocations during " Richard Acayan
2023-05-12 14:54 ` [PATCH v2 0/2] misc: fastrpc: Fixes for issues in userspace Srinivas Kandagatla
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=20230327210217.60948-1-mailingradian@gmail.com \
--to=mailingradian@gmail.com \
--cc=amahesh@qti.qualcomm.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.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