From: Christoph Hellwig <hch@lst.de>
To: joern@lazybastard.org, miquel.raynal@bootlin.com, richard@nod.at,
vigneshr@ti.com
Cc: linux-mtd@lists.infradead.org
Subject: RFC: decouple block2mtd from block layer internals
Date: Thu, 14 Oct 2021 16:52:05 +0200 [thread overview]
Message-ID: <20211014145206.1488967-1-hch@lst.de> (raw)
Hi all,
while looking for abuses of ->bd_inode, block2mtd scored high on the list.
This completely UNTESTED patch tries to move it off that and use the proper
file abstraction instead. Are there any current users of this code that
could give it a spin?
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2021-10-14 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 14:52 Christoph Hellwig [this message]
2021-10-14 14:52 ` [PATCH] mtd/block2mtd: don't poke into block layer internals Christoph Hellwig
2021-10-14 19:28 ` Richard Weinberger
2021-10-15 6:28 ` hch
2021-10-15 6:53 ` Miquel Raynal
2021-10-19 5:53 ` hch
2021-10-22 7:50 ` Richard Weinberger
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=20211014145206.1488967-1-hch@lst.de \
--to=hch@lst.de \
--cc=joern@lazybastard.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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