From: Christoph Hellwig <hch@infradead.org>
To: Daniel Golle <daniel@makrotopia.org>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jens Axboe" <axboe@kernel.dk>,
"Christian Brauner" <brauner@kernel.org>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Li Lingfeng" <lilingfeng3@huawei.com>,
"Ming Lei" <ming.lei@redhat.com>,
"Christian Heusel" <christian@heusel.eu>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Felix Fietkau" <nbd@nbd.name>, "John Crispin" <john@phrozen.org>,
"Chad Monroe" <chad.monroe@adtran.com>,
"Yangyu Chen" <cyy@cyyself.name>,
"Tianling Shen" <cnsztl@immortalwrt.org>,
"Chuanhong Guo" <gch981213@gmail.com>,
"Chen Minqiang" <ptpt52@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: [PATCH v5 3/4] block: add support for notifications
Date: Tue, 30 Jul 2024 12:36:59 -0700 [thread overview]
Message-ID: <ZqlA21iolCpnu4wn@infradead.org> (raw)
In-Reply-To: <ca0022886e8f211a323a716653a1396a3bc91653.1722365899.git.daniel@makrotopia.org>
Same NAK as last time. Random modules should not be able to hook
directly into block device / partition probing.
What you want to do can be done trivially in userspace in initramfs,
please do that as recommended multiple times before.
next prev parent reply other threads:[~2024-07-30 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 19:24 [PATCH v5 0/4] block: preparations for NVMEM provider Daniel Golle
2024-07-30 19:24 ` [PATCH v5 1/4] dt-bindings: block: add basic bindings for block devices Daniel Golle
2024-07-30 19:25 ` [PATCH v5 2/4] block: partitions: populate fwnode Daniel Golle
2024-07-30 19:26 ` [PATCH v5 3/4] block: add support for notifications Daniel Golle
2024-07-30 19:36 ` Christoph Hellwig [this message]
2024-07-30 21:28 ` Daniel Golle
2024-07-30 19:27 ` [PATCH v5 4/4] block: add new genhd flag GENHD_FL_NVMEM Daniel Golle
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=ZqlA21iolCpnu4wn@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=chad.monroe@adtran.com \
--cc=christian@heusel.eu \
--cc=cnsztl@immortalwrt.org \
--cc=conor+dt@kernel.org \
--cc=cyy@cyyself.name \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=gch981213@gmail.com \
--cc=john@phrozen.org \
--cc=krzk+dt@kernel.org \
--cc=lilingfeng3@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=nbd@nbd.name \
--cc=ptpt52@gmail.com \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).