linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pankaj Raghav <p.raghav@samsung.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: <axboe@kernel.dk>, <minchan@kernel.org>, <martin@omnibond.com>,
	<hubcap@omnibond.com>, <brauner@kernel.org>,
	<viro@zeniv.linux.org.uk>, <senozhatsky@chromium.org>,
	<akpm@linux-foundation.org>, <willy@infradead.org>, <hch@lst.de>,
	<devel@lists.orangefs.org>, <mcgrof@kernel.org>,
	<linux-block@vger.kernel.org>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>, <gost.dev@samsung.com>,
	<linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v2 1/5] zram: always chain bio to the parent in read_from_bdev_async
Date: Tue, 11 Apr 2023 09:34:28 +0200	[thread overview]
Message-ID: <2f718a2e-9fbd-831a-a505-cecb32140ab7@samsung.com> (raw)
In-Reply-To: <ZCw9Dxdd0C95EUza@infradead.org>

> 
> It will obviously conflict with this patch, so maybe the best thing is
> to get the other page_endio removals into their respective maintainer
> trees, and then just do the final removal of the unused function after
> -rc1.

Alright, I will drop the last patch that removes the page_endio function, and
send it after rc1. I will make the other changes as suggested by you.


  parent reply	other threads:[~2023-04-11  7:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230403132223eucas1p28adb1d36d39add989d46e9f175c07986@eucas1p2.samsung.com>
2023-04-03 13:22 ` [PATCH v2 0/5] remove page_endio() Pankaj Raghav
     [not found]   ` <CGME20230403132223eucas1p2a27e8239b8bda4fc16b675a9473fd61f@eucas1p2.samsung.com>
2023-04-03 13:22     ` [PATCH v2 1/5] zram: always chain bio to the parent in read_from_bdev_async Pankaj Raghav
2023-04-03 21:19       ` Minchan Kim
2023-04-04 15:06       ` Christoph Hellwig
2023-04-04 19:31         ` Andrew Morton
2023-04-05  6:07           ` Christoph Hellwig
2023-04-11  7:34         ` Pankaj Raghav [this message]
     [not found]   ` <CGME20230403132224eucas1p28f82802bc40d4feb5a30bb59c6536ab3@eucas1p2.samsung.com>
2023-04-03 13:22     ` [PATCH v2 2/5] orangefs: use folios in orangefs_readahead Pankaj Raghav
2023-04-04 15:07       ` Christoph Hellwig
     [not found]   ` <CGME20230403132224eucas1p21fd296fbd4af70220331bb19023f4169@eucas1p2.samsung.com>
2023-04-03 13:22     ` [PATCH v2 3/5] mpage: split bi_end_io callback for reads and writes Pankaj Raghav
2023-04-04 15:09       ` Christoph Hellwig
     [not found]   ` <CGME20230403132225eucas1p15848db3c850e950b21b339d5861080e1@eucas1p1.samsung.com>
2023-04-03 13:22     ` [PATCH v2 4/5] mpage: use folios in bio end_io handler Pankaj Raghav
2023-04-04 15:10       ` Christoph Hellwig
     [not found]   ` <CGME20230403132226eucas1p182e09f5da7bc0bd284d6a8494cd40903@eucas1p1.samsung.com>
2023-04-03 13:22     ` [PATCH v2 5/5] filemap: remove page_endio() Pankaj Raghav
2023-04-04 15:10       ` Christoph Hellwig

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=2f718a2e-9fbd-831a-a505-cecb32140ab7@samsung.com \
    --to=p.raghav@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=devel@lists.orangefs.org \
    --cc=gost.dev@samsung.com \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=hubcap@omnibond.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=martin@omnibond.com \
    --cc=mcgrof@kernel.org \
    --cc=minchan@kernel.org \
    --cc=senozhatsky@chromium.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox