[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZC0QCJM6Rl39jnGU@infradead.org>
Date: Tue, 4 Apr 2023 23:07:04 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Christoph Hellwig <hch@...radead.org>,
Pankaj Raghav <p.raghav@...sung.com>, axboe@...nel.dk,
minchan@...nel.org, martin@...ibond.com, hubcap@...ibond.com,
brauner@...nel.org, viro@...iv.linux.org.uk,
senozhatsky@...omium.org, willy@...radead.org, hch@....de,
devel@...ts.orangefs.org, mcgrof@...nel.org,
linux-block@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, gost.dev@...sung.com,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v2 1/5] zram: always chain bio to the parent in
read_from_bdev_async
On Tue, Apr 04, 2023 at 12:31:31PM -0700, Andrew Morton wrote:
> > I've now sent a series to untangle
> > and fix up the zram I/O path, which should address the underlying
> > issue here.
>
> I can't find that series.
https://lore.kernel.org/linux-block/20230404150536.2142108-1-hch@lst.de/T/#t
Powered by blists - more mailing lists