From: Christoph Hellwig <hch@lst.de>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@lst.de>,
axboe@kernel.dk, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] writeback: don't warn on an unregistered BDI in __mark_inode_dirty
Date: Wed, 9 Dec 2020 18:47:50 +0100 [thread overview]
Message-ID: <20201209174750.GA20352@lst.de> (raw)
In-Reply-To: <20201209163536.GA2587@quack2.suse.cz>
On Wed, Dec 09, 2020 at 05:35:36PM +0100, Jan Kara wrote:
> > I have a vague memory someone else sent this patch alredy, but couldn't
> > find it in my mailing list folder. But given that my current NVMe
> > tests trigger it easily I'd rather get it fixed ASAP.
>
> Did this patch get lost? I don't see it upstream or in Jens' tree. FWIW I
> agree the warning may result in false positive so I'm OK with removing it.
> So feel free to add:
>
> Reviewed-by: Jan Kara <jack@suse.cz>
Yes, it looks like this patch got lost somewhere again.
next prev parent reply other threads:[~2020-12-09 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 12:26 [PATCH] writeback: don't warn on an unregistered BDI in __mark_inode_dirty Christoph Hellwig
2020-12-09 16:35 ` Jan Kara
2020-12-09 17:47 ` Christoph Hellwig [this message]
2020-12-16 10:57 ` Jan Kara
2020-12-16 14:19 ` Jens Axboe
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=20201209174750.GA20352@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).