From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>, Tim Waugh <tim@cyberelk.net>,
linux-block@vger.kernel.org
Subject: Re: remove ->revalidate_disk (resend)
Date: Tue, 30 Mar 2021 07:28:37 +0200 [thread overview]
Message-ID: <20210330052837.GA4726@lst.de> (raw)
In-Reply-To: <465891ab-0633-2ee3-b51a-fe2e7be5f9ca@kernel.dk>
On Mon, Mar 29, 2021 at 07:01:54AM -0600, Jens Axboe wrote:
> On 3/28/21 11:55 PM, Christoph Hellwig wrote:
> > On Mon, Mar 08, 2021 at 08:45:47AM +0100, Christoph Hellwig wrote:
> >> Hi Jens,
> >>
> >> with the previously merged patches all real users of ->revalidate_disk
> >> are gone. This series removes the two remaining not actually required
> >> instances and the method itself.
> >
> > Jens,
> >
> > can you consider this for the 5.13 tree?
>
> Looks fine to me, we just need to drop the umem change as it was
> removed. And paride really should be as well... But in any case,
Last time asked around (for the blk-mq conversion) we still had people
actively using it.
> I'll queue up the other two or 5.13.
So this ended up on the drivers branch. I do have a buch of core
changes pending that will depend on it.
next prev parent reply other threads:[~2021-03-30 5:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 7:45 remove ->revalidate_disk (resend) Christoph Hellwig
2021-03-08 7:45 ` [PATCH 1/3] paride/pd: remove ->revalidate_disk Christoph Hellwig
2021-03-08 7:45 ` [PATCH 2/3] umem: " Christoph Hellwig
2021-03-08 7:45 ` [PATCH 3/3] block: remove the revalidate_disk method Christoph Hellwig
2021-03-29 5:55 ` remove ->revalidate_disk (resend) Christoph Hellwig
2021-03-29 13:01 ` Jens Axboe
2021-03-30 5:28 ` Christoph Hellwig [this message]
2021-06-16 9:41 ` chenxiang (M)
2021-06-16 13:50 ` Christoph Hellwig
2021-06-17 3:43 ` chenxiang (M)
2021-06-17 10:29 ` Christoph Hellwig
2021-06-17 11:50 ` chenxiang (M)
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=20210330052837.GA4726@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=tim@cyberelk.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.