[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20131023100303.GA20373@infradead.org>
Date: Wed, 23 Oct 2013 03:03:03 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Richard Weinberger <richard.weinberger@...il.com>
Cc: Christoph Hellwig <hch@...radead.org>,
David Woodhouse <dwmw2@...radead.org>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>, kirill@...temov.name
Subject: Re: [PATCH, RFC] what's the point of mtd_inodefs?
On Wed, Oct 23, 2013 at 07:50:17AM +0200, Richard Weinberger wrote:
> On Tue, Oct 22, 2013 at 5:33 PM, Christoph Hellwig <hch@...radead.org> wrote:
> > I've been looking at mtdchar as part of a bigger series touching all
> > kidns of places and really wonder what the point of mtd_inodefs is.
>
> As far I can tell it was introduced because of that issue:
> http://lists.infradead.org/pipermail/linux-mtd/2010-April/029593.html
Not sure how that issue came up as writeback only ever uses
mapping->backing_dev_info for block devices, else it only uses s_bdi to
avoid this issue. As pointed out somewhere in that thread the mem
driver uses a similar scheme.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists