From: Stefan Wahren <stefan.wahren@i2se.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
linux-kernel@vger.kernel.org
Cc: dan.carpenter@oracle.com, Eric Anholt <eric@anholt.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH v3 1/4] staging: vchiq_2835_arm: revert "quit using custom down_interruptible()"
Date: Wed, 15 May 2019 11:52:42 +0200 [thread overview]
Message-ID: <32aa420a-abff-4c47-5f3c-2d4bdf36781c@i2se.com> (raw)
In-Reply-To: <20190509143137.31254-2-nsaenzjulienne@suse.de>
On 09.05.19 16:31, Nicolas Saenz Julienne wrote:
> The killable version of down() is meant to be used on situations where
> it should not fail at all costs, but still have the convenience of being
> able to kill it if really necessary. VCHIQ doesn't fit this criteria, as
> it's mainly used as an interface to V4L2 and ALSA devices.
>
> Fixes: ff5979ad8636 ("staging: vchiq_2835_arm: quit using custom down_interruptible()")
> Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
This whole series is:
Acked-by: Stefan Wahren <stefan.wahren@i2se.com>
next prev parent reply other threads:[~2019-05-15 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 14:31 [PATCH v3 0/4] staging: vchiq: use interruptible waits Nicolas Saenz Julienne
2019-05-09 14:31 ` [PATCH v3 1/4] staging: vchiq_2835_arm: revert "quit using custom down_interruptible()" Nicolas Saenz Julienne
2019-05-15 9:52 ` Stefan Wahren [this message]
2019-05-09 14:31 ` [PATCH v3 2/4] staging: vchiq: revert "switch to wait_for_completion_killable" Nicolas Saenz Julienne
2019-05-09 14:31 ` [PATCH v3 3/4] staging: vchiq: make wait events interruptible Nicolas Saenz Julienne
2019-05-09 14:31 ` [PATCH v3 4/4] staging: vchiq: stop explicitly comparing with zero to catch errors Nicolas Saenz Julienne
2019-05-09 14:41 ` Dan Carpenter
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=32aa420a-abff-4c47-5f3c-2d4bdf36781c@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenzjulienne@suse.de \
/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®