From: Wolfram Sang <wsa@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v2 0/2] i2c: fortify the subsystem against user-space induced deadlocks
Date: Thu, 12 Jan 2023 10:09:22 +0100 [thread overview]
Message-ID: <Y7/OQiJCFzgnMnaG@ninjato> (raw)
In-Reply-To: <CAMRc=MfhVVN+W0Th8jdzTBHu6reFNpkm_cst3jMQZij0bDD=jQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 369 bytes --]
Hi Bart,
> It's been two weeks without any comments on this series and over a
> month since v1 so let me send a gentle ping on this.
This series has a priority for the next merge window. I love it!
However, patch 2 is difficult to review because I need to dive in deeply
into the topic. Hopes are that I can do this next week.
Thanks and happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-01-12 9:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 16:00 [PATCH v2 0/2] i2c: fortify the subsystem against user-space induced deadlocks Bartosz Golaszewski
2022-12-29 16:00 ` [PATCH v2 1/2] i2c: dev: fix notifier return values Bartosz Golaszewski
2023-01-17 10:04 ` Wolfram Sang
2023-03-08 16:58 ` Geert Uytterhoeven
2023-03-08 19:33 ` Bartosz Golaszewski
2023-03-08 19:51 ` Geert Uytterhoeven
2023-03-09 7:47 ` Geert Uytterhoeven
2022-12-29 16:00 ` [PATCH v2 2/2] i2c: dev: don't allow user-space to deadlock the kernel Bartosz Golaszewski
2023-01-17 10:08 ` Wolfram Sang
2023-01-17 10:10 ` Bartosz Golaszewski
2023-01-17 10:26 ` Wolfram Sang
2023-01-17 18:57 ` Wolfram Sang
2023-01-18 12:51 ` Bartosz Golaszewski
[not found] ` <20230118145914.3012-1-hdanton@sina.com>
2023-01-18 15:07 ` Bartosz Golaszewski
2023-01-12 9:01 ` [PATCH v2 0/2] i2c: fortify the subsystem against user-space induced deadlocks Bartosz Golaszewski
2023-01-12 9:09 ` Wolfram Sang [this message]
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=Y7/OQiJCFzgnMnaG@ninjato \
--to=wsa@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.