From: Kirill Smelkov <kirr@nexedi.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Julia Lawall <Julia.Lawall@lip6.fr>, Jan Blunck <jblunck@suse.de>,
Arnd Bergmann <arnd@arndb.de>, Jiri Kosina <jikos@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
<cocci@systeme.lip6.fr>, <linux-input@vger.kernel.org>,
<linux-iio@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PULL] stream_open bits for Linux 5.3
Date: Sun, 14 Jul 2019 14:13:46 +0000 [thread overview]
Message-ID: <20190714141317.GA20277@deco.navytux.spb.ru> (raw)
Linus,
Please consider pulling the following stream_open related bits:
This time on stream_open front it is only two small changes:
- the first one converts stream_open.cocci to treat all functions that
start with wait_.* as blocking. Previously it was only wait_event_.*
functions that were considered as blocking, but this was falsely
reporting deadlock cases as only warning. The patch was picked by
linux-kbuild and already entered your tree as 0c4ab18fc33b.
It is thus omitted from hereby pull-request.
- the second one teaches stream_open.cocci to consider files as being
stream-like even if they use noop_llseek. I posted this patch for
review 3 weeks ago[1], but got neither feedback nor complaints.
[1] https://lore.kernel.org/lkml/20190623072838.31234-2-kirr@nexedi.com/
The changes are available for pulling from here:
https://lab.nexedi.com/kirr/linux.git stream_open-5.3
Thanks beforehand,
Kirill
Kirill Smelkov (1):
*: convert stream-like files -> stream_open, even if they use noop_llseek
drivers/hid/hid-sensor-custom.c | 2 +-
drivers/input/mousedev.c | 2 +-
scripts/coccinelle/api/stream_open.cocci | 9 ++++++++-
3 files changed, 10 insertions(+), 3 deletions(-)
next reply other threads:[~2019-07-14 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 14:13 Kirill Smelkov [this message]
2019-07-15 0:30 ` pr-tracker-bot
2019-07-15 7:34 ` Kirill Smelkov
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=20190714141317.GA20277@deco.navytux.spb.ru \
--to=kirr@nexedi.com \
--cc=Julia.Lawall@lip6.fr \
--cc=arnd@arndb.de \
--cc=benjamin.tissoires@redhat.com \
--cc=cocci@systeme.lip6.fr \
--cc=dmitry.torokhov@gmail.com \
--cc=jblunck@suse.de \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--cc=yamada.masahiro@socionext.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®